[Python-checkins] devguide: Note Python 2.7 What's New maintenance changes

Sat Jun 21 13:19:48 CEST 2014

http://hg.python.org/devguide/rev/645c79611f32
changeset: 703:645c79611f32
user: Nick Coghlan <ncoghlan at gmail.com>
date: Sat Jun 21 21:19:39 2014 +1000
summary:
 Note Python 2.7 What's New maintenance changes
files:
 committing.rst | 15 ++++++++++++---
 1 files changed, 12 insertions(+), 3 deletions(-)

diff --git a/committing.rst b/committing.rst
--- a/committing.rst
+++ b/committing.rst
@@ -140,14 +140,16 @@
 http://www.python.org/psf/contrib/contrib-form/
 
 
-NEWS Entries
-------------
+What's New and NEWS Entries
+---------------------------
 
 Almost all changes made to the code base deserve an entry in ``Misc/NEWS``.
 If the change is particularly interesting for end users (e.g. new features,
 significant improvements, or backwards-incompatible changes), an entry in
 the ``What's New in Python`` document (in ``Doc/whatsnew/``) should be added
-as well. There are two notable exceptions to this general principle, and they
+as well.
+
+There are two notable exceptions to this general principle, and they
 both relate to changes that *already* have a NEWS entry, and have not yet
 been included in any formal release (including alpha and beta releases).
 These exceptions are:
@@ -161,6 +163,13 @@
 and the original NEWS entry remains valid, then no additional entry is
 needed.
 
+Needing a What's New entry almost always means that a change is *not*
+suitable for inclusion in a maintenance release. A small number of
+exceptions have been made for Python 2.7 due to the long support period -
+when implemented, these changes *must* be noted in the "New Additions in
+Python 2.7 Maintenance Releases" section of the Python 2.7 What's New
+document.
+
 New NEWS entries are customarily added at or near the top of their
 respective sections, so that entries within a section appear in approximate
 order from newest to oldest. However, this is customary and not a
-- 
Repository URL: http://hg.python.org/devguide
