diff options
| author | Michael Wallner <mike@php.net> | 2013-12-19 10:08:27 +0100 |
|---|---|---|
| committer | Michael Wallner <mike@php.net> | 2013-12-19 10:08:27 +0100 |
| commit | 17470df2a508fc5b8aaaf10cd97673d5aa133692 (patch) | |
| tree | 3ee2184ceec94b82f245f00fdb8cc2033d88f591 | |
| parent | 436ca2d019ed3ec3183129f9a3a7e329446077e9 (diff) | |
| parent | 391fe528b71a20e16c0eae08bd99fa8f95ce00b6 (diff) | |
| download | php-git-17470df2a508fc5b8aaaf10cd97673d5aa133692.tar.gz | |
Merge branch 'PHP-5.5' into PHP-5.6
* PHP-5.5:
Update NEWS handling section of README.GIT-RULES
| -rw-r--r-- | README.GIT-RULES | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/README.GIT-RULES b/README.GIT-RULES index 6e90aa97b6..3df9d17bcd 100644 --- 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 |