Éric Araujo mer...@netwok.org added the comment:
The whole file is ordered with newest on top (newest Python version), so I
guess it’s implicit for all committers that sections are also ordered with
newest on top. It does not actually matter; the contents of one “what’s new in
Python W.XyZ”
Chris Jerdonek chris.jerdo...@gmail.com added the comment:
Patch attached. I moved the discussion of NEWS entries to a section before the
discussion on commit messages because previously, the commit message discussion
referenced NEWS entries before they had been discussed (and not vice
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset bbe197bf57a1 by Ned Deily in branch 'default':
Issue #15260: Expand information on Misc/NEWS entries.
http://hg.python.org/devguide/rev/bbe197bf57a1
--
nosy: +python-dev
Ned Deily n...@acm.org added the comment:
Thanks for the patch!
--
nosy: +ned.deily
resolution: - fixed
stage: - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15260
New submission from Chris Jerdonek chris.jerdo...@gmail.com:
I think it would help if the Commit Messages and NEWS Entries subsection of
the Developer's Guide said something about where in the ordering new Misc/NEWS
entries should be added (e.g. at the top or bottom or by importance):
