You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xerces.apache.org by mr...@apache.org on 2005/10/13 05:55:26 UTC
svn commit: r320639 - in /xerces/java/trunk/docs: bugzilla.xml
faq-contributing.xml install.xml
Author: mrglavas
Date: Wed Oct 12 20:55:21 2005
New Revision: 320639
URL: http://svn.apache.org/viewcvs?rev=320639&view=rev
Log:
Replace all references to CVS with SVN.
Modified:
xerces/java/trunk/docs/bugzilla.xml
xerces/java/trunk/docs/faq-contributing.xml
xerces/java/trunk/docs/install.xml
Modified: xerces/java/trunk/docs/bugzilla.xml
URL: http://svn.apache.org/viewcvs/xerces/java/trunk/docs/bugzilla.xml?rev=320639&r1=320638&r2=320639&view=diff
==============================================================================
--- xerces/java/trunk/docs/bugzilla.xml (original)
+++ xerces/java/trunk/docs/bugzilla.xml Wed Oct 12 20:55:21 2005
@@ -29,7 +29,7 @@
with to see whether the bug has been already reported and/or fixed.
You can also download the
<jump href='http://vmgump.apache.org/gump/public-jars/xml-xerces2/'>latest code</jump>
- in CVS and check if you can reproduce the bug.</li>
+ in SVN and check if you can reproduce the bug.</li>
<li>Report bugs against the newest release.</li>
<li>Read <jump href="http://issues.apache.org/jira">JIRA Notes</jump></li>
</ul>
Modified: xerces/java/trunk/docs/faq-contributing.xml
URL: http://svn.apache.org/viewcvs/xerces/java/trunk/docs/faq-contributing.xml?rev=320639&r1=320638&r2=320639&view=diff
==============================================================================
--- xerces/java/trunk/docs/faq-contributing.xml (original)
+++ xerces/java/trunk/docs/faq-contributing.xml Wed Oct 12 20:55:21 2005
@@ -29,7 +29,7 @@
<ol>
<li>Check out and build the most recent Xerces code. For
instructions on how to do this, see <jump
- href="http://xml.apache.org/cvs.html">Apache XML Project CVS
+ href="http://xml.apache.org/svn.html">Apache Xerces Project SVN
Information</jump>. If you do this, you can confirm that your
bug still exists and has not been fixed since the last
release.
@@ -48,8 +48,8 @@
<li>
Prepare a patch to fix Xerces code. To do this, when you
have applied your changes to a local copy of the most
- recent xerces source code, do <code>cvs diff -u
- file</code> for each file you've changed.
+ recent xerces source code, do <code>svn diff
+ file</code> for each file you've changed.
</li>
<li>
Zip (or tar) up your patches. If you send them in the
@@ -96,7 +96,7 @@
Also, the release manager should attempt to ensure that appropriate
credit has been given for contributions).
</li>
- <li>Tag the release in CVS
+ <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
@@ -122,7 +122,7 @@
<li>zip and tar the tools directory</li>
<li>
Generate PGP/GNUPG signatures for dist binaries:<br/>
- That is, add public key to the CVS <code>KEYS</code> file if necessary
+ That is, add public key to the SVN <code>KEYS</code> file if necessary
and make sure public key is on a key server or two.
</li>
<li>Upload the binaries and signatures to the dist section of
@@ -139,15 +139,15 @@
it's a big enough release, announcements@xml.apache.org and
announcements@apache.org
</li>
- <li>Bugzilla :<br/>
+ <li>JIRA:<br/>
Firstly, create new release. Then,
remove oldest release (if we are up-to 6
releases).
</li>
<li>Website:<br/>
Upload generated docs directory to daedalus (until this process
- matures and becomes CVS-based).
- Commit <code>/www/xml.apache.org/xerces2-j</code> to CVS;
+ matures and becomes SVN-based).
+ Commit <code>/www/xml.apache.org/xerces2-j</code> to SVN;
i.e., update the xml-site module.
</li>
</ol>
Modified: xerces/java/trunk/docs/install.xml
URL: http://svn.apache.org/viewcvs/xerces/java/trunk/docs/install.xml?rev=320639&r1=320638&r2=320639&view=diff
==============================================================================
--- xerces/java/trunk/docs/install.xml (original)
+++ xerces/java/trunk/docs/install.xml Wed Oct 12 20:55:21 2005
@@ -279,10 +279,10 @@
Obtain a copy of the public key of the Xerces
committer. While most committers have posted their
keys to public "key servers", probably the easiest
- place to get them from is CVS. The public keys of
+ place to get them from is SVN. The public keys of
all Xerces committers who post releases are available
from the file called <code>KEYS</code> located in the
- root directory of the <code>xml-xerces/java</code>
+ root directory of the <code>http://svn.apache.org/repos/asf/xerces/java/trunk/</code>
repository.
</li>
<li>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xerces.apache.org
For additional commands, e-mail: commits-help@xerces.apache.org