httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j..@apache.org
Subject svn commit: r169386 - in /httpd/site/trunk: docs/dev/devnotes.html xdocs/dev/devnotes.xml
Date Tue, 10 May 2005 00:21:02 GMT
Author: jsl
Date: Mon May  9 17:21:02 2005
New Revision: 169386

URL: http://svn.apache.org/viewcvs?rev=169386&view=rev
Log:
First round hack at dev/devnotes.xml.

Modified:
    httpd/site/trunk/docs/dev/devnotes.html
    httpd/site/trunk/xdocs/dev/devnotes.xml

Modified: httpd/site/trunk/docs/dev/devnotes.html
URL: http://svn.apache.org/viewcvs/httpd/site/trunk/docs/dev/devnotes.html?rev=169386&r1=169385&r2=169386&view=diff
==============================================================================
--- httpd/site/trunk/docs/dev/devnotes.html (original)
+++ httpd/site/trunk/docs/dev/devnotes.html Mon May  9 17:21:02 2005
@@ -71,33 +71,75 @@
            <table border="0" cellspacing="0" cellpadding="2" width="100%">
  <tr><td bgcolor="#525D76">
   <font color="#ffffff" face="arial,helvetica,sanserif">
+   <strong>Overview</strong>
+  </font>
+ </td></tr>
+ <tr><td>
+  <blockquote>
+<p>The Apache HTTP Server Project has switched to Subversion for hosting its
+source code.</p>
+<p>To check out the 2.0.x branch:</p>
+<blockquote>
+<code>
+svn co http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x httpd-2.0.x
+</code>
+</blockquote>
+<p>To check out the 1.3.x branch:</p>
+<blockquote>
+<code>
+svn co http://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x httpd-1.3.x
+</code>
+</blockquote>
+<p>To check out the current development version (as of this writing, 2.1.x),
+use:</p>
+<blockquote>
+<code>
+svn co http://svn.apache.org/repos/asf/httpd/httpd/trunk httpd-trunk
+</code>
+</blockquote>
+<p>Committers should check out via https instead of http (so that they can
+commit their changes).  For more info about Subversion, please read <a href="http://www.apache.org/dev/version-control.html">the
ASF version control FAQ</a>.</p>
+<p>The developers continue to seek to maintain module compatibility between
+2.0.42 and future 2.0 releases for administrators and end users, while
+continuing the forward progress that has made the 2.0 server faster and more
+scalable.</p>
+  </blockquote>
+ </td></tr>
+</table>
+           <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
+  <font color="#ffffff" face="arial,helvetica,sanserif">
    <strong>Maintaining the Sources</strong>
   </font>
  </td></tr>
  <tr><td>
   <blockquote>
 <p>Almost all files relating to Apache, either the actual sources or the
-files that aren't part of the distribution, are maintained in a
-<a href="http://www.cvshome.org/">CVS</a> repository.  Here is the way in 
-which changes are applied:</p>
+files that aren't part of the distribution, are now maintained in an
+<a href="http://subversion.tigris.org/">SVN</a> repository.  Here is the way
+in which changes are applied:</p>
 <ol>
    <li>Developer checks out a copy of the files on which it wants to
-    work, into a private working directory:
+    work (in this case, the trunk), into a private working directory
+    called <samp>httpd-trunk</samp>:
     <p>
     <dl>
-     <dd><samp>% cvs checkout apache</samp>
+     <dd><samp>% svn co http://svn.apache.org/repos/asf/httpd/httpd/trunk
+      httpd-trunk</samp>
      </dd>
     </dl>
     </p>
     <p>
-    This step only needs to be performed once.
+    This step only needs to be performed once (unless the private working
+    directory is tainted or deleted.)  Committers should use a URI prefix
+    of <samp>https</samp> on the checkout, to save themselves headaches later.
     </p>
    </li>
-   <li>Developer keeps its working directory synchronised with changes
+   <li>Developer keeps his/her working directory synchronised with changes
     made to the repository:
     <p>
     <dl>
-     <dd><samp>% cvs update apache</samp>
+     <dd><samp>% svn up httpd-trunk</samp>
      </dd>
     </dl>
     </p>
@@ -111,12 +153,13 @@
     them:
     <p>
     <dl>
-     <dd><samp>% cvs diff -u apache/src/mod_mime.c &gt; /tmp/foo</samp>
+     <dd><samp>% svn diff httpd-trunk/modules/http/mod_mime.c &gt; /tmp/foo</samp>
      </dd>
     </dl>
     </p>
     <p>
-    The <samp>/tmp/foo</samp> file is mailed to the developers list so
+    The <samp>/tmp/foo</samp> file is mailed to the
+    <a href="http://httpd.apache.org/lists.html#http-dev">developers list</a>
so
     they can consider the value/validity of the patch.  It is also worth
     making sure your code follows the Apache style, as described by the
     GNU indent flags in the .indent.pro file in every source directory.
@@ -126,7 +169,7 @@
     Thing, the developer checks the changes into the repository:
     <p>
     <dl>
-     <dd><samp>% cvs commit apache/src/mod_mime.c</samp>
+     <dd><samp>% svn commit httpd-trunk/modules/http/mod_mime.c</samp>
      </dd>
     </dl>
     </p>
@@ -138,24 +181,29 @@
            <table border="0" cellspacing="0" cellpadding="2" width="100%">
  <tr><td bgcolor="#525D76">
   <font color="#ffffff" face="arial,helvetica,sanserif">
-   <strong>CVS Modules</strong>
+   <strong>SVN Modules</strong>
   </font>
  </td></tr>
  <tr><td>
   <blockquote>
-<p>There are several different modules in the Apache CVS repository:</p>
+<p>There are several different branches under the <samp>httpd</samp>
+   module in the Apache SVN repository that pertain to the different
+   releases.  The top level can be perused with the
+   <a href="http://svn.apache.org/viewcvs.cgi/">SVN ViewCVS</a> pages.
+   The main modules pertaining to the <samp>httpd</samp> server source
+   are:</p>
 <table border="0" cellspacing="0" cellpadding="2" width="100%">
  <tr><td bgcolor="#828DA6">
   <font color="#ffffff" face="arial,helvetica,sanserif">
-   <strong>apache-1.3</strong>
+   <strong>httpd-1.3</strong>
   </font>
  </td></tr>
  <tr><td>
   <blockquote>
 <p>To create a directory tree containing the 1.3 sources,
-  and call it <samp>apache-1.3</samp>, change your current directory
-  to the <em>parent</em> of the tree and then check the 1.3 sources
-  out as follows:</p>
+    and call it <samp>apache-1.3</samp>, change your current directory
+    to the <em>parent</em> of the tree and then check the 1.3 sources
+    out as follows:</p>
 <div align="left">
   <table cellspacing="4" cellpadding="0" border="0">
     <tr>
@@ -167,7 +215,7 @@
       <td bgcolor="#023264" width="1"><img src="/images/void.gif" width="1" height="1"
vspace="0" hspace="0" border="0"/></td>
       <td bgcolor="#ffffff"><pre>
 % cd /usr/local/apache
-% cvs checkout apache-1.3</pre></td>
+% svn co http://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x apache-1.3</pre></td>
       <td bgcolor="#023264" width="1"><img src="/images/void.gif" width="1" height="1"
vspace="0" hspace="0" border="0"/></td>
     </tr>
     <tr>
@@ -189,9 +237,9 @@
  <tr><td>
   <blockquote>
 <p>To create a directory tree containing the 2.0 sources,
-  and call it <samp>httpd-2.0</samp>, change your current directory
-  to the <em>parent</em> of the tree and then check the 2.0 sources
-  out as follows:</p>
+    and call it <samp>httpd-2.0</samp>, change your current directory
+    to the <em>parent</em> of the tree and then check the 2.0 sources
+    out as follows:</p>
 <div align="left">
   <table cellspacing="4" cellpadding="0" border="0">
     <tr>
@@ -203,10 +251,7 @@
       <td bgcolor="#023264" width="1"><img src="/images/void.gif" width="1" height="1"
vspace="0" hspace="0" border="0"/></td>
       <td bgcolor="#ffffff"><pre>
 % cd /usr/local/apache
-% cvs checkout -d httpd-2.0 -r APACHE_2_0_BRANCH httpd-2.0
-% cd httpd-2.0/srclib
-% cvs checkout -r APR_0_9_BRANCH apr
-% cvs checkout -r APU_0_9_BRANCH apr-util</pre></td>
+% svn co http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x httpd-2.0</pre></td>
       <td bgcolor="#023264" width="1"><img src="/images/void.gif" width="1" height="1"
vspace="0" hspace="0" border="0"/></td>
     </tr>
     <tr>
@@ -216,11 +261,6 @@
     </tr>
   </table>
 </div>
-<p>The httpd-2.0 repository takes advantage of APR and APR-util from the
-  Apache portable run-time, so those must be checked out separately.
-  Because not all httpd contributors have access to APR, you may need to
-  use anonymous CVS to get those repositories.  We are looking in to 
-  solving this problem.</p>
   </blockquote>
  </td></tr>
 </table>
@@ -232,8 +272,9 @@
  </td></tr>
  <tr><td>
   <blockquote>
-<p>If you want to check out the bleeding edge of development, the httpd-2.1
-  development tree (slated for a release 2.2), use cvs HEAD as follows:</p>
+<p>If you want to check out the bleeding edge of development, the
+     httpd-2.1 development tree (slated for a release 2.2), and call it
+     <samp>httpd-trunk</samp>, checkout as follows:</p>
 <div align="left">
   <table cellspacing="4" cellpadding="0" border="0">
     <tr>
@@ -245,9 +286,7 @@
       <td bgcolor="#023264" width="1"><img src="/images/void.gif" width="1" height="1"
vspace="0" hspace="0" border="0"/></td>
       <td bgcolor="#ffffff"><pre>
 % cd /usr/local/apache
-% cvs checkout -d httpd-2.1 httpd-2.0
-% cd httpd-2.1/srclib
-% cvs checkout apr apr-util</pre></td>
+% svn co http://svn.apache.org/repos/asf/httpd/httpd/trunk httpd-trunk</pre></td>
       <td bgcolor="#023264" width="1"><img src="/images/void.gif" width="1" height="1"
vspace="0" hspace="0" border="0"/></td>
     </tr>
     <tr>
@@ -263,45 +302,28 @@
 <table border="0" cellspacing="0" cellpadding="2" width="100%">
  <tr><td bgcolor="#828DA6">
   <font color="#ffffff" face="arial,helvetica,sanserif">
-   <strong>site</strong>
-  </font>
- </td></tr>
- <tr><td>
-  <blockquote>
-<p>This module contains the files that live at
-  <samp>http://www.apache.org/</samp>.  The directory on the host that
-  maps to that URL is actually a set of checked-out working copies of
-  the CVS files.</p>
-<make_note>
-     It is important that the files on the Web host not be modified
-     directly.  If you want or need to change one, check it out into a
-     private working copy, modify <strong>that</strong>, commit the
-     change into CVS, and then perform a <samp>cvs update -dP</samp> to
-     bring the host directory into sync with the CVS sources.
-  </make_note>
-<p>
-    The Web site directories are <em>not</em> maintained in synch with
-    the CVS files automatically.  They are manually updated from CVS by
-    various people as they consider appropriate.  This is usually not an
-    issue, unless a group of files are being updated according to an
-    ongoing group discussion.
-    </p>
-  </blockquote>
- </td></tr>
-</table>
-<table border="0" cellspacing="0" cellpadding="2" width="100%">
- <tr><td bgcolor="#828DA6">
-  <font color="#ffffff" face="arial,helvetica,sanserif">
    <strong>httpd-site</strong>
   </font>
  </td></tr>
  <tr><td>
   <blockquote>
-<p>Like the <samp>site</samp> module, this one is used to 
-    maintain the files that comprise a website - in this case,
-    <samp>http://httpd.apache.org/</samp>.  Also like the previous module,
-    the directory on the server is a checked-out working copy of this
-    module.</p>
+<p>This module contains the files that live at <samp>http://httpd.apache.org/</samp>.
+    The directory on the host that maps to that URL is actually a set of
+    checked-out working copies of the SVN files.</p>
+<p>The SVN URI is
+    <samp>https://svn.apache.org/repos/asf/httpd/site/trunk/docs</samp>.</p>
+<make_note>
+    It is important that the files on the Web host not be modified
+    directly.  If you want or need to change one, check it out into a
+    private working copy, modify <strong>that</strong>, commit the
+    change into SVN, and then perform a <samp>svn update</samp> to
+    bring the host directory into sync with the SVN sources.
+   </make_note>
+<p>The Web site <em>directories</em> (as opposed to files) are not
+    maintained in synch with the SVN files automatically.  They are
+    manually updated from SVN by various people as they consider
+    appropriate.  This is usually not an issue, unless a group of files
+    are being updated according to an ongoing group discussion.</p>
   </blockquote>
  </td></tr>
 </table>
@@ -313,7 +335,7 @@
  </td></tr>
  <tr><td>
   <blockquote>
-<p>Like the <samp>site</samp> module, this one is used ot
+<p>Like the <samp>httpd-site</samp> module, this one is used to
     maintain the files that comprise a website - in this case,
     <samp>http://www.apache.org/dist/httpd/</samp>.  Also like the
     previous module, the directory on the server is a checked-out
@@ -321,6 +343,15 @@
     directory, we only have the surrounding documentation and control
     files checked into this module -- the actual tarballs are simply
     copied to www.apache.org.</p>
+<p>The SVN URI is
+    <samp>https://svn.apache.org/repos/asf/httpd/httpd/dist</samp>.</p>
+<p>Committers would generally deal with this module when "rolling" a
+    release.  This is a series of steps that comprise an actual new
+    release of the Apache httpd software.  Amongst other things, the
+    key to this module is the <samp>tools/</samp> directory, which
+    contains the <samp>release.sh</samp> shell script.  More information
+    on the policies and procedures relating to rolling releases can be
+    found on the <a href="release.html">Release Guidelines</a> page.</p>
   </blockquote>
  </td></tr>
 </table>
@@ -330,70 +361,15 @@
            <table border="0" cellspacing="0" cellpadding="2" width="100%">
  <tr><td bgcolor="#525D76">
   <font color="#ffffff" face="arial,helvetica,sanserif">
-   <strong>Setting Up Remote CVS</strong>
-  </font>
- </td></tr>
- <tr><td>
-  <blockquote>
-<p>Most of the Apache Group members with access to the CVS repository
-actually do their work on their local machines and keep synchronised
-with the repository through remote CVS.  See the <a href="http://httpd.apache.org/about_apache.html">ABOUT
APACHE</a>
-page for information about how the group works and people get access
-to the CVS repository.)  One way to set this up using the
-<a href="http://www.ssh.fi/sshprotocols2/index.html"><samp>ssh</samp></a>

-(secure shell) tool:</p>
-<ol>
-  <li><strong><em>You need an account on the Apache repository
-    system.</em></strong>  
-    If you've been "voted in" for direct access to the 
-    repository, this should have been set up for you.
-    (You know if you have it.)
-   </li>
-   <li>Include the following in your login files on your
-     <strong>local</strong> (UNIX) machine:
-     <pre>
-       setenv CVSROOT <em>repository-system</em>:/home/cvs
-       setenv CVS_RSH /usr/local/bin/ssh
-       setenv CVS_SERVER /usr/local/bin/cvs
-    </pre>
-    Adjust the last two paths to correctly reflect the locations of
-    <samp>cvs</samp> and <samp>ssh</samp> on your local system.
-   </li>
-   <li><p>Set up the following environment in your account on the Apache
-    repository system:</p>
-    <pre>
-      setenv CVSROOT /home/cvs
-      setenv CVS_RSH /usr/local/bin/ssh
-      setenv CVS_SERVER /usr/local/bin/cvs
-    </pre>
-    <p>These <em>are</em> the correct locations for the repository system,
-    so you don't need to edit them.</p>
-   </li>
-   <li>On your local system generate your SSH public key file 
-    <samp>~/.ssh/identity.pub</samp> via <samp>ssh-keygen</samp>
and then put
-    it in <samp>~/.ssh/authorized_keys</samp> on the repository system. If you
-    use the <samp>ssh-agent</samp> this will allow you to access the repository
-    without having to enter a password for each CVS operation. Use
-    <samp>ssh-add</samp> and enter your passphrase once when you start a
-    session, and <samp>ssh-add -D</samp> at the end of the session to
-    delete your unencrypted key(s) from the agent.
-   </li>
-  </ol>
-  </blockquote>
- </td></tr>
-</table>
-           <table border="0" cellspacing="0" cellpadding="2" width="100%">
- <tr><td bgcolor="#525D76">
-  <font color="#ffffff" face="arial,helvetica,sanserif">
-   <strong>Working with the Apache Source CVS Repository remotely</strong>
+   <strong>Setting Up Remote SVN</strong>
   </font>
  </td></tr>
  <tr><td>
   <blockquote>
-<p>Ralf Engelschall has written an excellent explanation on how to use
-remote CVS with the "cvsup" functionality we have available now.</p>
-<p><a href="http://www.engelschall.com/pw/apache/cvsguide/">
-http://www.engelschall.com/pw/apache/cvsguide/</a></p>
+<p>A brief overview of getting started with SVN committer access can be
+found <a href="http://www.apache.org/dev/version-control.html#https-svn">
+here</a>.  One key change to note is that SSH is not used anymore for
+committer access, due to the functional differences with SVN.</p>
   </blockquote>
  </td></tr>
 </table>

Modified: httpd/site/trunk/xdocs/dev/devnotes.xml
URL: http://svn.apache.org/viewcvs/httpd/site/trunk/xdocs/dev/devnotes.xml?rev=169386&r1=169385&r2=169386&view=diff
==============================================================================
--- httpd/site/trunk/xdocs/dev/devnotes.xml (original)
+++ httpd/site/trunk/xdocs/dev/devnotes.xml Mon May  9 17:21:02 2005
@@ -13,31 +13,76 @@
 </section>
 
 <section>
+<title>Overview</title>
+
+<p>The Apache HTTP Server Project has switched to Subversion for hosting its
+source code.</p>
+
+<p>To check out the 2.0.x branch:</p>
+<blockquote>
+<code>
+svn co http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x httpd-2.0.x
+</code>
+</blockquote>
+
+<p>To check out the 1.3.x branch:</p>
+
+<blockquote>
+<code>
+svn co http://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x httpd-1.3.x
+</code>
+</blockquote>
+
+<p>To check out the current development version (as of this writing, 2.1.x),
+use:</p>
+
+<blockquote>
+<code>
+svn co http://svn.apache.org/repos/asf/httpd/httpd/trunk httpd-trunk
+</code>
+</blockquote>
+
+<p>Committers should check out via https instead of http (so that they can
+commit their changes).  For more info about Subversion, please read <a
+href="http://www.apache.org/dev/version-control.html"
+>the ASF version control FAQ</a>.</p>
+
+<p>The developers continue to seek to maintain module compatibility between
+2.0.42 and future 2.0 releases for administrators and end users, while
+continuing the forward progress that has made the 2.0 server faster and more
+scalable.</p>
+</section>
+
+<section>
 <title>Maintaining the Sources</title>
 
 <p>Almost all files relating to Apache, either the actual sources or the
-files that aren't part of the distribution, are maintained in a
-<a href="http://www.cvshome.org/">CVS</a> repository.  Here is the way in 
-which changes are applied:</p>
+files that aren't part of the distribution, are now maintained in an
+<a href="http://subversion.tigris.org/">SVN</a> repository.  Here is the way
+in which changes are applied:</p>
 
   <ol>
    <li>Developer checks out a copy of the files on which it wants to
-    work, into a private working directory:
+    work (in this case, the trunk), into a private working directory
+    called <samp>httpd-trunk</samp>:
     <p>
     <dl>
-     <dd><samp>% cvs checkout apache</samp>
+     <dd><samp>% svn co http://svn.apache.org/repos/asf/httpd/httpd/trunk
+      httpd-trunk</samp>
      </dd>
     </dl>
     </p>
     <p>
-    This step only needs to be performed once.
+    This step only needs to be performed once (unless the private working
+    directory is tainted or deleted.)  Committers should use a URI prefix
+    of <samp>https</samp> on the checkout, to save themselves headaches later.
     </p>
    </li>
-   <li>Developer keeps its working directory synchronised with changes
+   <li>Developer keeps his/her working directory synchronised with changes
     made to the repository:
     <p>
     <dl>
-     <dd><samp>% cvs update apache</samp>
+     <dd><samp>% svn up httpd-trunk</samp>
      </dd>
     </dl>
     </p>
@@ -51,12 +96,13 @@
     them:
     <p>
     <dl>
-     <dd><samp>% cvs diff -u apache/src/mod_mime.c &gt; /tmp/foo</samp>
+     <dd><samp>% svn diff httpd-trunk/modules/http/mod_mime.c &gt; /tmp/foo</samp>
      </dd>
     </dl>
     </p>
     <p>
-    The <samp>/tmp/foo</samp> file is mailed to the developers list so
+    The <samp>/tmp/foo</samp> file is mailed to the
+    <a href="http://httpd.apache.org/lists.html#http-dev">developers list</a>
so
     they can consider the value/validity of the patch.  It is also worth
     making sure your code follows the Apache style, as described by the
     GNU indent flags in the .indent.pro file in every source directory.
@@ -66,7 +112,7 @@
     Thing, the developer checks the changes into the repository:
     <p>
     <dl>
-     <dd><samp>% cvs commit apache/src/mod_mime.c</samp>
+     <dd><samp>% svn commit httpd-trunk/modules/http/mod_mime.c</samp>
      </dd>
     </dl>
     </p>
@@ -75,78 +121,65 @@
 </section>
 
 <section>
-<title>CVS Modules</title>
-  <p>There are several different modules in the Apache CVS repository:</p>
-
-  <section><title>apache-1.3</title>
-  <p>To create a directory tree containing the 1.3 sources,
-  and call it <samp>apache-1.3</samp>, change your current directory
-  to the <em>parent</em> of the tree and then check the 1.3 sources
-  out as follows:</p>
-  <source>
+<title>SVN Modules</title>
+  <p>There are several different branches under the <samp>httpd</samp>
+   module in the Apache SVN repository that pertain to the different
+   releases.  The top level can be perused with the
+   <a href="http://svn.apache.org/viewcvs.cgi/">SVN ViewCVS</a> pages.
+   The main modules pertaining to the <samp>httpd</samp> server source
+   are:</p>
+
+  <section><title>httpd-1.3</title>
+   <p>To create a directory tree containing the 1.3 sources,
+    and call it <samp>apache-1.3</samp>, change your current directory
+    to the <em>parent</em> of the tree and then check the 1.3 sources
+    out as follows:</p>
+   <source>
 % cd /usr/local/apache
-% cvs checkout apache-1.3</source>
+% svn co http://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x apache-1.3</source>
   </section>
 
   <section><title>httpd-2.0</title>
-  <p>To create a directory tree containing the 2.0 sources,
-  and call it <samp>httpd-2.0</samp>, change your current directory
-  to the <em>parent</em> of the tree and then check the 2.0 sources
-  out as follows:</p>
-  <source>
+   <p>To create a directory tree containing the 2.0 sources,
+    and call it <samp>httpd-2.0</samp>, change your current directory
+    to the <em>parent</em> of the tree and then check the 2.0 sources
+    out as follows:</p>
+   <source>
 % cd /usr/local/apache
-% cvs checkout -d httpd-2.0 -r APACHE_2_0_BRANCH httpd-2.0
-% cd httpd-2.0/srclib
-% cvs checkout -r APR_0_9_BRANCH apr
-% cvs checkout -r APU_0_9_BRANCH apr-util</source>
-  <p>The httpd-2.0 repository takes advantage of APR and APR-util from the
-  Apache portable run-time, so those must be checked out separately.
-  Because not all httpd contributors have access to APR, you may need to
-  use anonymous CVS to get those repositories.  We are looking in to 
-  solving this problem.</p>
+% svn co http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x httpd-2.0</source>
   </section>
 
   <section><title>httpd-2.1</title>
-<p>If you want to check out the bleeding edge of development, the httpd-2.1
-  development tree (slated for a release 2.2), use cvs HEAD as follows:</p>
-  <source>
+   <p>If you want to check out the bleeding edge of development, the
+     httpd-2.1 development tree (slated for a release 2.2), and call it
+     <samp>httpd-trunk</samp>, checkout as follows:</p>
+   <source>
 % cd /usr/local/apache
-% cvs checkout -d httpd-2.1 httpd-2.0
-% cd httpd-2.1/srclib
-% cvs checkout apr apr-util</source>
-  </section>
-
-  <section><title>site</title>
-  <p>This module contains the files that live at
-  <samp>http://www.apache.org/</samp>.  The directory on the host that
-  maps to that URL is actually a set of checked-out working copies of
-  the CVS files.</p>
-  <make_note>
-     It is important that the files on the Web host not be modified
-     directly.  If you want or need to change one, check it out into a
-     private working copy, modify <strong>that</strong>, commit the
-     change into CVS, and then perform a <samp>cvs update -dP</samp> to
-     bring the host directory into sync with the CVS sources.
-  </make_note>
-    <p>
-    The Web site directories are <em>not</em> maintained in synch with
-    the CVS files automatically.  They are manually updated from CVS by
-    various people as they consider appropriate.  This is usually not an
-    issue, unless a group of files are being updated according to an
-    ongoing group discussion.
-    </p>
+% svn co http://svn.apache.org/repos/asf/httpd/httpd/trunk httpd-trunk</source>
   </section>
 
   <section><title>httpd-site</title>
-   <p>Like the <samp>site</samp> module, this one is used to 
-    maintain the files that comprise a website - in this case,
-    <samp>http://httpd.apache.org/</samp>.  Also like the previous module,
-    the directory on the server is a checked-out working copy of this
-    module.</p>
+   <p>This module contains the files that live at <samp>http://httpd.apache.org/</samp>.
+    The directory on the host that maps to that URL is actually a set of
+    checked-out working copies of the SVN files.</p>
+   <p>The SVN URI is
+    <samp>https://svn.apache.org/repos/asf/httpd/site/trunk/docs</samp>.</p>
+   <make_note>
+    It is important that the files on the Web host not be modified
+    directly.  If you want or need to change one, check it out into a
+    private working copy, modify <strong>that</strong>, commit the
+    change into SVN, and then perform a <samp>svn update</samp> to
+    bring the host directory into sync with the SVN sources.
+   </make_note>
+   <p>The Web site <em>directories</em> (as opposed to files) are not
+    maintained in synch with the SVN files automatically.  They are
+    manually updated from SVN by various people as they consider
+    appropriate.  This is usually not an issue, unless a group of files
+    are being updated according to an ongoing group discussion.</p>
   </section>
 
   <section><title>httpd-dist</title>
-   <p>Like the <samp>site</samp> module, this one is used ot
+   <p>Like the <samp>httpd-site</samp> module, this one is used to
     maintain the files that comprise a website - in this case,
     <samp>http://www.apache.org/dist/httpd/</samp>.  Also like the
     previous module, the directory on the server is a checked-out
@@ -154,68 +187,25 @@
     directory, we only have the surrounding documentation and control
     files checked into this module -- the actual tarballs are simply
     copied to www.apache.org.</p>
+   <p>The SVN URI is
+    <samp>https://svn.apache.org/repos/asf/httpd/httpd/dist</samp>.</p>
+   <p>Committers would generally deal with this module when "rolling" a
+    release.  This is a series of steps that comprise an actual new
+    release of the Apache httpd software.  Amongst other things, the
+    key to this module is the <samp>tools/</samp> directory, which
+    contains the <samp>release.sh</samp> shell script.  More information
+    on the policies and procedures relating to rolling releases can be
+    found on the <a href="release.html">Release Guidelines</a> page.</p>
   </section>
 </section>
 
 <section>
-<title>Setting Up Remote CVS</title>
-
-<p>Most of the Apache Group members with access to the CVS repository
-actually do their work on their local machines and keep synchronised
-with the repository through remote CVS.  See the <a
-href="http://httpd.apache.org/about_apache.html">ABOUT APACHE</a>
-page for information about how the group works and people get access
-to the CVS repository.)  One way to set this up using the
-<a href="http://www.ssh.fi/sshprotocols2/index.html"><samp>ssh</samp></a>

-(secure shell) tool:</p>
-
-<ol>
-  <li><strong><em>You need an account on the Apache repository
-    system.</em></strong>  
-    If you've been &quot;voted in&quot; for direct access to the 
-    repository, this should have been set up for you.
-    (You know if you have it.)
-   </li>
-   <li>Include the following in your login files on your
-     <strong>local</strong> (UNIX) machine:
-     <pre>
-       setenv CVSROOT <em>repository-system</em>:/home/cvs
-       setenv CVS_RSH /usr/local/bin/ssh
-       setenv CVS_SERVER /usr/local/bin/cvs
-    </pre>
-    Adjust the last two paths to correctly reflect the locations of
-    <samp>cvs</samp> and <samp>ssh</samp> on your local system.
-   </li>
-   <li><p>Set up the following environment in your account on the Apache
-    repository system:</p>
-    <pre>
-      setenv CVSROOT /home/cvs
-      setenv CVS_RSH /usr/local/bin/ssh
-      setenv CVS_SERVER /usr/local/bin/cvs
-    </pre>
-    <p>These <em>are</em> the correct locations for the repository system,
-    so you don't need to edit them.</p>
-   </li>
-   <li>On your local system generate your SSH public key file 
-    <samp>~/.ssh/identity.pub</samp> via <samp>ssh-keygen</samp>
and then put
-    it in <samp>~/.ssh/authorized_keys</samp> on the repository system. If you
-    use the <samp>ssh-agent</samp> this will allow you to access the repository
-    without having to enter a password for each CVS operation. Use
-    <samp>ssh-add</samp> and enter your passphrase once when you start a
-    session, and <samp>ssh-add -D</samp> at the end of the session to
-    delete your unencrypted key(s) from the agent.
-   </li>
-  </ol>
-</section>
-
-<section>
-<title>Working with the Apache Source CVS Repository remotely</title>
-
-<p>Ralf Engelschall has written an excellent explanation on how to use
-remote CVS with the "cvsup" functionality we have available now.</p>
+<title>Setting Up Remote SVN</title>
 
-<p><a href="http://www.engelschall.com/pw/apache/cvsguide/">
-http://www.engelschall.com/pw/apache/cvsguide/</a></p>
+<p>A brief overview of getting started with SVN committer access can be
+found <a href="http://www.apache.org/dev/version-control.html#https-svn">
+here</a>.  One key change to note is that SSH is not used anymore for
+committer access, due to the functional differences with SVN.</p>
 </section>
 
 </body>



Mime
View raw message