I seldom look at TDE changelogs so I don't know the precise timeline but I'm pretty sure there are some changes missing.
Is this a bug I should report?
--Mike
# zcat /usr/share/doc/tdebase-trinity/changelog.Debian.gz | head -13 tdebase-trinity (4:14.0.11~pre51-0debian11.0.0+7) bullseye; urgency=low
* Automated git build for a13485e3059e968b89b09d74bc4967f4843783ff
-- Slávek Banko slavek.banko@axis.cz Mon, 11 Oct 2021 10:15:13 +0200
tdebase-trinity (4:3.5.10-2ubuntu12) karmic; urgency=low
* Repaired kdesktop crash on load * Fixed tderandrtray crash when randr X extension is unavailable * Added option to keys config dialog to alter Win key from modifier status
-- Timothy Pearson kb9vqf@pearsoncomputing.net Mon, 07 Dec 2009 13:24:00 -0600
Dne st 13. října 2021 Mike Bird napsal(a):
I seldom look at TDE changelogs so I don't know the precise timeline but I'm pretty sure there are some changes missing.
Is this a bug I should report?
--Mike
# zcat /usr/share/doc/tdebase-trinity/changelog.Debian.gz | head -13 tdebase-trinity (4:14.0.11~pre51-0debian11.0.0+7) bullseye; urgency=low
- Automated git build for a13485e3059e968b89b09d74bc4967f4843783ff
-- Slávek Banko slavek.banko@axis.cz Mon, 11 Oct 2021 10:15:13 +0200
tdebase-trinity (4:3.5.10-2ubuntu12) karmic; urgency=low
- Repaired kdesktop crash on load
- Fixed tderandrtray crash when randr X extension is unavailable
- Added option to keys config dialog to alter Win key from modifier
status
-- Timothy Pearson kb9vqf@pearsoncomputing.net Mon, 07 Dec 2009 13:24:00 -0600 ____________________________________________________
Hi Mike,
this is not a bug directly, but the result of the way the source packages are created. Creating is done in this way that an appropriate folder from tde-packaging is added to the source tarball and the current record is added to debian/changelog. Because there is no sense to add a complete listing of the git log into debian/changelog, it is only added a record referring to the appropriate git version. And because such a record is not valuable to be regularly saved back into tde-packaging, debian/changelog is in a long term without significant changes.
Is the question of whether we could find a reasonable way in which to generate reasonably valuable information to debian/changelog? We can also discuss the rules how to do the updates of changelog in tde-packaging.
Cheers
On Wed October 13 2021 06:04:11 Slávek Banko wrote:
Is the question of whether we could find a reasonable way in which to generate reasonably valuable information to debian/changelog? We can also discuss the rules how to do the updates of changelog in tde-packaging.
Hi Slávek,
It's rare that I need to look at changelogs and rarer still I need to look at anything but the most recent entry and if I need more there is git.
So my opinion doesn't really matter and I'll leave the changelog handling to you and the other active developers.
Thanks,
--Mike
Dne st 13. října 2021 Mike Bird napsal(a):
On Wed October 13 2021 06:04:11 Slávek Banko wrote:
Is the question of whether we could find a reasonable way in which to generate reasonably valuable information to debian/changelog? We can also discuss the rules how to do the updates of changelog in tde-packaging.
Hi Slávek,
It's rare that I need to look at changelogs and rarer still I need to look at anything but the most recent entry and if I need more there is git.
So my opinion doesn't really matter and I'll leave the changelog handling to you and the other active developers.
Thanks,
--Mike ____________________________________________________
Possible for maintanance releases, we could add to changelog the link to detailed changelog on wiki. For example:
https://wiki.trinitydesktop.org/Changelog_For_R14.0.11#tdelibs
What do you think about it?
Cheers
On Wed October 13 2021 07:47:59 Slávek Banko wrote:
Possible for maintanance releases, we could add to changelog the link to detailed changelog on wiki. For example:
https://wiki.trinitydesktop.org/Changelog_For_R14.0.11#tdelibs
What do you think about it?
Perfect!