morgand 01/04/13 12:44:00
Modified: . HOWTO-RELEASE
Log:
decided to use the same version number examples throughout
Revision Changes Path
1.2 +6 -6 jakarta-taglibs/HOWTO-RELEASE
Index: HOWTO-RELEASE
===================================================================
RCS file: /home/cvs/jakarta-taglibs/HOWTO-RELEASE,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- HOWTO-RELEASE 2001/04/13 19:35:49 1.1
+++ HOWTO-RELEASE 2001/04/13 19:44:00 1.2
@@ -29,22 +29,22 @@
1.2 STARTING/COMPLETING MAJOR RELEASES
-Let's assume that the current release of your tag library is 3.0.4, but you want to
start work on 4.0. Here are the steps you would take to start working on the new
release:
+Let's assume that the current release of your tag library is 2.0.4, but you want to
start work on 3.0. Here are the steps you would take to start working on the new
release:
1) Make an announcement on taglibs-dev
- 2) Create a branch called dev4 in CVS for the entire tag library
+ 2) Create a branch called dev3 in CVS for the entire tag library
3) Work on that branch
(Note: it is a requirement that the main CVS branch in CVS be the _current_
release, not a prospective release.)
-Once the 4.0 version is ready for release to the public, you would do this:
+Once the 3.0 version is ready for release to the public, you would do this:
1) Call a release vote on taglibs-dev
2) After receiving approval, migrate the current main trunk
- to a branch called rel3
- 3) Merge the dev4 branch to the main trunk
+ to a branch called rel2
+ 3) Merge the dev3 branch to the main trunk
-The version 4 release is now the main trunk of the CVS tree. However, versions 3,
2, and 1 will still be available on other branches (rel3, rel2, and rel1), if other
releases of that version prove necessary.
+The version 3 release is now the main trunk of the CVS tree. However, versions 2
and 1 will still be available on other branches (rel2 and rel1), if other releases of
that version prove necessary.
2 NEWS
