Gesendet: Montag, 16. Oktober 2017 um 11:10 Uhr Von: "Michael Ströder" <michael@stroeder.com> An: opensuse-packaging <opensuse-packaging@opensuse.org> Betreff: [opensuse-packaging] .changes madness with upstream updates
HI!
Sometimes a submission of me gets declined because of changelog being too short or too long referring to this policy:
https://en.opensuse.org/openSUSE:Creating_a_changes_file_%28RPM%29#What_goes...
While the guide-lines were surely outlined with good aims I have to question the current policy of package changelogs (*.changes) regarding upstream updates. The rules are too blurry and boil down to "Do the right thing".
I don't like to provide an extract of an upstream changelog because I'm convinced that no packager is capable of extracting a really meaningful essence from an upstream changelog. Furthermore I assume that upstream developers are also lazy writing docs and the changelog would have been already shorter if still meaningful.
*See Mercurial Change Log for Details* is a common phrase I see in 'my' upstream packages. We had a lengthy discussion on this, and the developers are not willing to change this
So IMO the right way is to..
- just mention upstream release and packaging changes
xor
- add the complete changelog.
I vote for 1)! Best Axel -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org