morgand 01/04/16 08:37:26
Modified: . HOWTO-RELEASE
Log:
no message
Revision Changes Path
1.3 +5 -8 jakarta-taglibs/HOWTO-RELEASE
Index: HOWTO-RELEASE
===================================================================
RCS file: /home/cvs/jakarta-taglibs/HOWTO-RELEASE,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- HOWTO-RELEASE 2001/04/13 19:44:00 1.2
+++ HOWTO-RELEASE 2001/04/16 15:37:25 1.3
@@ -32,19 +32,16 @@
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 dev3 in CVS for the entire tag library
- 3) Work on that branch
+ 2) Create a branch called rel2 in CVS for the entire tag library,
+ which will preserve the currently released version
+ 3) Continue work for the 3.0 release on the MAIN branch
-(Note: it is a requirement that the main CVS branch in CVS be the _current_
release, not a prospective release.)
-
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 rel2
- 3) Merge the dev3 branch to the main trunk
+ 2) After receiving approval, build the release jar and place it on the site
-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.
+The version 3 release is 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
