Quoting pgajdos@suse.cz:
On Wed, Aug 29, 2012 at 02:42:51PM +0200, Dominique Leuenberger a.k.a DimStar wrote:
- .Changes entries
Can I do small statistics here?
Please do rpm -q --changelog man-pages
Do you like changelog entries before update to 3.34 or after update to 3.33?
Honestly? BOTH are nonsense. Try to settle somewhere in between. My initial mail said about .changes: ************************************ A simple "Update to version x.y.z" is, as before, not accepted. There should be some buzz around the update for the user; some major reasons to the upgrade should be listed Changes on the package itself should be mentioned in a way that any other contributor to the same package can follow traces of why something is the way it is. Commonly, Added (build)dependencies are interesting to be seen, special hacks to make something work in a particular way [..]: Always consider that package maintenance is a distributed task and various contributors need to be able to step up at will. "some buzz" does not mean every single line from a ChangeLog needs to be copied.. Very often, the 'right' balance for an update can be found in an Announcement (where upstream usually also tries to explain to their users why they believe it's worthy to update). For your example of man-pages a .changes like this for 3.41 might have been more suitable: + Update to version 3.41: - A new get_robust_list(2) page documents the get_robust_list() and set_robust_list() system calls. - Three new pages ? mallinfo(3), malloc_info(3), and malloc_stats(3) ? document various interfaces used to monitor the state of the malloc implementation. - The madvise(2) page adds documentation of the MADV_DONTDUMP and MADV_DODUMP operations Dominique (I did not look at any specifics for spec changes that would require documentation.. but I trust that was outside of your question anyway). -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org