This is an automated email from the ASF dual-hosted git repository.
elharo pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/xerces-j.git
The following commit(s) were added to refs/heads/main by this push:
new 39d71e542 Update contributing FAQ by removing old API refresh steps
(#77)
39d71e542 is described below
commit 39d71e542ad90446d93ebcdb6b67f6e9055b8212
Author: Elliotte Rusty Harold <[email protected]>
AuthorDate: Sun Mar 1 09:02:26 2026 -0500
Update contributing FAQ by removing old API refresh steps (#77)
* Update contributing FAQ by removing old API refresh steps
Removed outdated instructions for refreshing API code.
* Simplify release tagging instructions in FAQ
Removed redundant instructions for tagging the current branch of
xml-commons.
---
docs/faq-contributing.xml | 13 +------------
1 file changed, 1 insertion(+), 12 deletions(-)
diff --git a/docs/faq-contributing.xml b/docs/faq-contributing.xml
index 0d4a848cc..a2f9b3206 100644
--- a/docs/faq-contributing.xml
+++ b/docs/faq-contributing.xml
@@ -75,14 +75,6 @@
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 (September 2, 2007) this was the main
- <code>trunk</code>.
- </li>
<li>Change the following files:<br/>
<code>build.xml</code>
(that is, change the <code>parser.Version</code>,
@@ -98,10 +90,7 @@
</li>
<li>Tag the release in SVN
(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 APIs that the parser needs to conform
- to; see step 1 above.
+ where x.y.z is the Xerces-J release number).
</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]
