Update NEWS handling section of README.GIT-RULES

See http://marc.info/?t=138124004400005&r=1&w=2
gyx1000 · Dec 19, 2013 · 3624a9c · 3624a9c
1 parent 2303d0e
commit 3624a9c
Showing 1 changed file with 5 additions and 3 deletions.
diff --git a/README.GIT-RULES b/README.GIT-RULES
@@ -69,9 +69,11 @@ The next few rules are more of a technical nature::
       branches) an empty merge should be done.
 
    2. All news updates intended for public viewing, such as new features,
-      bug fixes, improvements, etc., should go into the NEWS file of the
-      *first* to be released version with the given change. In other words
-      any NEWS file change only needs to done in one branch.
+      bug fixes, improvements, etc., should go into the NEWS file of *any
+      stable release* version with the given change. In other words,
+      news about a bug fix which went into PHP-5.4, PHP-5.5 and master
+      should be noted in both PHP-5.4/NEWS and PHP-5.5/NEWS but
+      not master, which is not a public released version yet.
 
    3. Do not commit multiple file and dump all messages in one commit. If you
       modified several unrelated files, commit each group separately and