Author: rdonkin
Date: Sun Feb 13 11:02:53 2005
New Revision: 153654
URL: http://svn.apache.org/viewcvs?view=rev&rev=153654
Log:
Converted instructions to subversion
Modified:
jakarta/commons/proper/commons-build/trunk/xdocs/releases/release.xml
Modified: jakarta/commons/proper/commons-build/trunk/xdocs/releases/release.xml
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/commons-build/trunk/xdocs/releases/release.xml?view=diff&r1=153653&r2=153654
==============================================================================
--- jakarta/commons/proper/commons-build/trunk/xdocs/releases/release.xml
(original)
+++ jakarta/commons/proper/commons-build/trunk/xdocs/releases/release.xml Sun
Feb 13 11:02:53 2005
@@ -60,17 +60,21 @@
<subsection name='2 Update CVS to Release Tag'>
<p>
- The release code should already have been tagged. Update the CVS checkout
- (from which the release will be cut) to this tagged version.
- </p>
+ The release code should already have been tagged.
+ A tag (in subversion) is just a history-preserving copy.
+ To access the tagged code, you need to checkout all directories
+ for the component, not just the trunk directory.
+ </p>
+ <pre>
+$ svn co https://svn.apache.org/repos/asf/jakarta/commons/proper/foo
+ </pre>
+ <p>
+ All tags are organized under the <code>tags</code> directory.
+
+ </p>
<pre>
-$ cd jakarta-commons/foo/
-$ cvs -q up -A
-$ cvs -q up -r FOO_1_2
+$ cd foo/tags/FOO_1_2
</pre>
- <p>
- Check the build number (to make sure that the update worked correctly).
This can be found in the <code>build.xml</code> file.
- </p>
</subsection>
<subsection name="3 Build Binary Distribution">
@@ -112,11 +116,7 @@
<li>
Export the tagged release:
<pre>
-$ cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic login
-Logging in to :pserver:[EMAIL PROTECTED]:/home/cvspublic
-CVS password: (anoncvs)
-
-$ cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic export -r FOO_1_2
jakarta-commons
+$ svn export
https://svn.apache.org/repos/asf/jakarta/commons/proper/logging/tags/FOO_1_2
</pre>
</li>
<li>
@@ -197,7 +197,7 @@
<p>
If this is the first release you've cut for this component, then the code
signing public key
must be added to the <a href='#Check KEYS file'><code>KEYS</code> file for the
component</a>.
-This can be found on Daedelus (www.apache.org) at
+This can be found on Minotaur (www.apache.org) at
<pre>
/www/www.apache.org/dist/jakarta/commons/logging/foo/KEYS
</pre>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
