On 16 October 2017 at 11:10, Michael Ströder <michael@stroeder.com> wrote:
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.
So IMO the right way is to..
1. just mention upstream release and packaging changes
xor
2. add the complete changelog.
Ciao, Michael.
I disagree with 2. - a complete changelog is too much My personal feeling is as follows: - Minimal acceptable - just mention upstream release and packaging changes - Ideal - upstream release, packaging changes and packagers "highlights" of release if the package maintainer is confident they have a meaningful understanding (I have more faith than you ;)) - Alternative - upstream release, packaging changes, and URL to full release notes. I personally consider my .changes entry to be 'too long' and start feeling uncomfortable if its starting to exceed 5 lines of content, and will absolutely force myself to refactor what I'm typing once I've hit line 10 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org