diff options
| author | Julien Pauli <jpauli@php.net> | 2015-07-29 10:04:33 +0200 |
|---|---|---|
| committer | Julien Pauli <jpauli@php.net> | 2015-07-29 10:04:33 +0200 |
| commit | d7f354fa573abfa7c54d397b3a7acae7f4ae6d29 (patch) | |
| tree | f691cfcdfe44e5c48ca74b9755c1fa4c7fcf29ac | |
| parent | 9fdb8c2ccd109ddc30bd46f0bd0c493352756b76 (diff) | |
| parent | 66edc158755a8e960499913f16f6455797bb5803 (diff) | |
| download | php-git-d7f354fa573abfa7c54d397b3a7acae7f4ae6d29.tar.gz | |
Merge branch 'PHP-5.5' into PHP-5.6
* PHP-5.5:
Adjust Git-Rules
5.4.44 next
| -rw-r--r-- | README.GIT-RULES | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/README.GIT-RULES b/README.GIT-RULES index 843c61ea63..c1c256dcf1 100644 --- a/README.GIT-RULES +++ b/README.GIT-RULES @@ -12,7 +12,7 @@ Collaboration is a Good Thing(tm), and Git lets us do this. Thus, following some basic rules with regards to Git usage will:: a. Make everybody happier, especially those responsible for maintaining - Git itself. + PHP itself. b. Keep the changes consistently well documented and easily trackable. @@ -48,11 +48,11 @@ Currently we have the following branches in use:: PHP-5.6 Is used to release the PHP 5.6.x series. This is a current stable version and is open for bugfixes only. - PHP-5.5 Is used to release the PHP 5.5.x series. This is a current - stable version and is open for bugfixes only. + PHP-5.5 Is used to release the PHP 5.5.x series. This is an old + stable version and is open for security fixes only. - PHP-5.4 Is used to release the PHP 5.4.x series. This is a current - stable version and is open for bugfixes only. + PHP-5.4 Is used to release the PHP 5.4.x series. This is an old + stable version and is open for security fixes only. PHP-5.3 This branch is closed. @@ -67,7 +67,7 @@ Currently we have the following branches in use:: The next few rules are more of a technical nature:: - 1. All changes should first go to the lowest branch (i.e. 5.4) and then + 1. All changes should first go to the lowest branch (i.e. 5.6) and then get merged up to all other branches. If a change is not needed for later branches (i.e. fixes for features which where dropped from later branches) an empty merge should be done. |