You are viewing a plain text version of this content. The canonical link for it is here.
Posted to batik-dev@xmlgraphics.apache.org by vh...@apache.org on 2001/07/31 19:18:59 UTC
cvs commit: xml-batik MAINTAIN
vhardy 01/07/31 10:18:58
Modified: . MAINTAIN
Log:
Updated build instructions.
Revision Changes Path
1.4 +48 -9 xml-batik/MAINTAIN
Index: MAINTAIN
===================================================================
RCS file: /home/cvs/xml-batik/MAINTAIN,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- MAINTAIN 2001/03/31 01:32:45 1.3
+++ MAINTAIN 2001/07/31 17:18:58 1.4
@@ -17,15 +17,54 @@
For creating a distribution the following steps must be done:
- 1) modify build.xml with the distribution version
- 2) run the build script with target "dist-zip" and "dist-tgz"
- 3) test the distributions
- 4) commit the version change to CVS
- 5) tag the release on CVS (cvs rtag <tag> <module>, e.g.,
- cvs rtag 1_0beta2 xml-batik)
- 6) connect to xml.apache.org with your account
- 7) scp the distributions under /www/xml.apache.org/dist/[project]/
- e.g., scp batik-1.0beta2.zip vhardy@xml.apache.org:/www/xml/apache.org/dist/batik/
+ 1) modify build.xml with the distribution version. Only modify for main
+ releases (e.g. 1.1) but not for release candidates (e.g. 1.1rc3)
+
+ 2) tag the release on CVS:
+ cvs rtag <tag> <module>
+ e.g., cvs rtag batik-1_1rc3 xml-batik.
+ Note: sometimes, it is necessary to remove a tag because the
+ tests failed and a fix was required. To remove a tag, use
+ the rtag command:
+ cvs rtag -d <tag> <module>
+ e.g., cvs rtag -d batik-1_1rc3 xml-batik
+
+ 3) checkout the tagged release:
+ cvs -r <tag> co xml-batik
+ e.g., cvs -r batik-1_1rc3 co xml-batik
+
+ 4) run the build script with target "dist-zip"
+ build dist-zip
+ this will create the binary release zip, the source release zip and the
+ javadoc zip.
+
+ 5) test the distributions
+ build regard
+ The build results are in xml-batik/test-reports. Check that there
+ are no show-stoppers for the release. If there are fixes required,
+ you need to remove the tag (as explained in step 2) and then fix
+ any problem that requires attention. Then, you need to start at
+ step 1) again.
+
+ Note that you will need to have a copy of the W3C SVG
+ working group test suite in the 'beSuite' directory and
+ have that directory under the same root as xml-batik. See
+ http://www.w3.org/Graphics/SVG for instructions on how to get
+ the SVG test suite.
+
+ 5) Update the README file describing the content of the release and
+ the modifications which have taken place:
+ http://xml.apache.org/batik/dist/README
+
+ 6) - If you are creating a release candidate, rename the distribution files
+ to an rc name. For example:
+ mv batik-src-1.1.zip batik-src-1.1rc1.zip
+
+ - scp the distributions and the README under /www/xml.apache.org/dist/batik/
+ e.g., scp batik-1.1rc1.zip vhardy@xml.apache.org:/www/xml.apache.org/dist/batik/
+
+ 7) send an email to the batik-dev and batik-users mailing lists announcing the
+ release.
Site Creation
-------------
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: batik-dev-help@xml.apache.org