On 10/16/2017 11:10 AM, Michael Ströder wrote:
1. just mention upstream release and packaging changes
xor
2. add the complete changelog.
Sometimes the only change in version update is an entry in .changes file and upstream tarball update. Sometimes it's a little more. But in both cases the correct way to manage the .changes changelog is to put in important changes for openSUSE users in there. If you only mention packages changes and no upstream changes, then users don't know what improvements happened, if any. Upstream changes could include security fixes, CVE numbers and other things that are important to track. Ideally, the .changes files should capture all the important changes upstream has done in the release. As to what is important, that's for you to filter. *Read* upstream changelog and decide. But in every release, try to find something in addition to "New upstream version X.Y.Z" and include that in the .changes. If nothing else, it at least makes your package look well maintained ;) Cheers, Adam -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org