neilg 2003/03/20 10:58:30
Modified: java/docs faq-contributing.xml
Log:
update release-preparation instructions so that they mention xml-commons dependencies
Revision Changes Path
1.2 +11 -0 xml-xerces/java/docs/faq-contributing.xml
Index: faq-contributing.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/faq-contributing.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- faq-contributing.xml 27 Mar 2002 22:09:29 -0000 1.1
+++ faq-contributing.xml 20 Mar 2003 18:58:30 -0000 1.2
@@ -60,6 +60,14 @@
follow these steps and you'll be done in no time:
</p>
<ol>
+ <li>Ensure that the API code has been properly refreshed.
+ That is, make sure that <code>tools/xml-apis.jar</code>
+ and <code>tools/xml-apis--src.zip</code> reflect the
+ state of the branch of xml-commons that contains the API
+ set to which the parser must conform. At the time of
+ writing (March 20, 2003) this was the branch
+ <code>tck-jaxp-1_2_0</code>.
+ </li>
<li>Change the following files:<br/>
<code>build.xml</code>
(that is, change the <code>parser.Version</code>,
@@ -76,6 +84,9 @@
<li>Tag the release in CVS
(tags for releases usually have the form Xerces-J_x_y_z
where x.y.z is the Xerces-J release number)
+ You should also tag the current branch of xml-commons
+ containing the API's that the parser needs to conform
+ to; see step 1 above.
</li>
<li>Do a test build and regression test run;
i.e., <code>build test</code> at a bare minimum.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
