On Thursday 2018-09-20 01:05, Jimmy Berry wrote:
On Wednesday, September 19, 2018 5:33:41 PM CDT Neal Gompa wrote:
It might also help if we didn't let people put ridiculously awful changelog entries (often generated by source services or something) due to the (IMO) odd desire to put lots of upstream changelog details from VCS history. I don't even bother to review some packages' changelogs on my computer anymore because too many packages make functionally useless changelogs because they just copy VCS history in, which is too much...
If one says "Update to version 1.2.3" with a link to upstream changelogs that will be denied. IMO changelogs should contain RPM specific changes, spec reworking, new exposed features, build flag changes, etc, but leave upstream to upstream.
Everything you say is - I hope - codified already in the Recommendation Page[1] (edits are welcome). [1] https://en.opensuse.org/openSUSE:Creating_a_changes_file_(RPM) "You can use SCM commit messages, if they prove to be useful. If in doubt, don't." "Be concise. Pick only the topmost interesting points:" (== new exposed features - or perhaps the antithesis of that which seriously broke/changed something) But even figuring out the new exposed features (or lack thereof and saying so with a single statement in the .changes) is something that some people seem to be totally overwhelmed with. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org