diff options
| author | Justin Erenkrantz <jerenkrantz@apache.org> | 2002-10-19 17:30:15 +0000 |
|---|---|---|
| committer | Justin Erenkrantz <jerenkrantz@apache.org> | 2002-10-19 17:30:15 +0000 |
| commit | 22cfb9d8c0333fd409b3e08d9fe5756aa0842415 (patch) | |
| tree | 0c29eff526d7436ff23c0dff28ee1b424286e66f /ROADMAP | |
| parent | d9306ff3855c85281bb9a4c5a50fe76670194a02 (diff) | |
| download | httpd-22cfb9d8c0333fd409b3e08d9fe5756aa0842415.tar.gz | |
Split out the stable and development release strategy.
(We don't need a constipated release strategy for unstable trees.)
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@97263 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'ROADMAP')
| -rw-r--r-- | ROADMAP | 32 |
1 files changed, 20 insertions, 12 deletions
@@ -1,6 +1,6 @@ APACHE 2.x ROADMAP ================== -Last modified at [$Date: 2002/10/18 16:58:14 $] +Last modified at [$Date: 2002/10/19 17:30:15 $] INTRODUCTION @@ -76,6 +76,16 @@ keeping the stable tree as safe as possible: tree, there is really no reason for this tree to be broken for more than a few minutes during a lengthy commit. +In order to avoid 'skipped' release numbers in the stable releases, the +Release Manager will generally roll a release candidate (APACHE_#_#_#_RC#) +tag. Release Candidate tarballs will be announced to the +stable-testers@httpd.apache.org for the stable tree. Then, the participants +will vote on the quality of the proposed release tarball. + +The final APACHE_#_#_# tag will not exist until the APACHE_#_#_#_RC# candidate +has passed the usual votes to release that version. Only then is the final +tarball packaged, removing all -rc# designations from the version number, and +tagging the tree with the release number. DEVELOPMENT RELEASES, 2.{odd}.{revision} ----------------------------------------- @@ -123,19 +133,17 @@ begun, that API will be present for the lifetime of the stable release. Any desired changes in the stable versions must wait for inclusion into the next release cycle. +In order to ease the burden of creating development releases, the process +for packaging a development releases is less formal than for the stable +release. This strategy reflects the fact that while in development, versions +are cheap. Development releases may be classified as alpha, beta, or GA +to reflect the group's perceived stability of the tree. Development releases +may be made at any time by any committer. -ALL RELEASES ------------- -In order to avoid 'skipped' release numbers, the Release Manager will generally -roll a release candidate (APACHE_#_#_#_RC#) tag. This is true of both the -stable as well as the development tree. Release Candidate tarballs will be -announced to the stable-testers@httpd.apache.org for the stable tree, or to -the current-testers@httpd.apache.org list for the development tree. +Please read the following link for a more detailed description of the +development release strategy: -The final APACHE_#_#_# tag will not exist until the APACHE_#_#_#_RC# candidate -has passed the usual votes to release that version. Only then is the final -tarball packaged, removing all -rc# designations from the version number, and -tagging the tree with the release number. +http://httpd.apache.org/dev/release.html WORKS IN PROGRESS |