httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From erikab...@apache.org
Subject cvs commit: httpd-site/xdocs/dev release.xml
Date Tue, 14 Oct 2003 15:57:53 GMT
erikabele    2003/10/14 08:57:53

  Modified:    docs/dev release.html
               xdocs/dev release.xml
  Log:
  Correct some mistakes.
  
  Revision  Changes    Path
  1.9       +10 -9     httpd-site/docs/dev/release.html
  
  Index: release.html
  ===================================================================
  RCS file: /home/cvs/httpd-site/docs/dev/release.html,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- release.html	15 Sep 2003 15:08:37 -0000	1.8
  +++ release.html	14 Oct 2003 15:57:53 -0000	1.9
  @@ -81,8 +81,8 @@
     <blockquote>
   <p>Technically, any one can make a release of the source code due to the
   <a href="http://www.apache.org/LICENSE.txt">Apache Software License</a>.
  -However, only members of the Apache HTTP Server Project (committers) to
  -project can make a release designated with Apache.  Other people must
  +However, only members of the Apache HTTP Server Project (committers)
  +can make a release designated with Apache.  Other people must
   call their release something other than "Apache" unless they obtain
   written permission from the Apache Software Foundation.</p>
   <p>Following our official release policies, we will only accept release
  @@ -116,7 +116,7 @@
              <table border="0" cellspacing="0" cellpadding="2" width="100%">
    <tr><td bgcolor="#525D76">
     <font color="#ffffff" face="arial,helvetica,sanserif">
  -   <strong>Who may make a good candidate for RM?</strong>
  +   <strong>Who may make a good candidate for an RM?</strong>
     </font>
    </td></tr>
    <tr><td>
  @@ -124,7 +124,7 @@
   <p>Someone with lots of time to kill.  Being an RM is a very important job
   in our community because it takes a fair amount of time to produce a stable
   release.  If you feel lucky, a release could be distributed without testing,
  -but our experience has shown that leads to a higher number of <i>dud</i>
  +but our experience has shown that this leads to a higher number of <i>dud</i>
   releases.  In general, our experience has shown that a well-coordinated
   release fares better than non-coordinated releases.</p>
     </blockquote>
  @@ -186,7 +186,7 @@
   <p>Committers <i>may</i> voluntarily refrain from committing patches
if
   they wish to ease the burden on the RM, but they are under
   <font color="red">no</font> obligation to do so.  This is one reason why we
  -recommend that the RM have plenty of time on their hands - they may have to
  +recommend that the RMs have plenty of time on their hands - they may have to
   deal with a rapidly changing target.  It's not an easy job.</p>
     </blockquote>
    </td></tr>
  @@ -229,11 +229,12 @@
   <p>Key points:</p>
   <ul>
   <li>Ensure that the RM's PGP/GPG key is in the httpd-dist/KEYS file</li>
  -<li>Create an official APACHE_X_Y_Z tag based of the candidate tree</li>
  -<li>Run httpd-dist/tools/release.sh script</li>
  +<li>Create an official APACHE_X_Y_Z tag based on the candidate tree</li>
  +<li>Run the httpd-dist/tools/release.sh script</li>
   <li>Copy the generated release tarballs and signatures to
  -daedalus:/www/httpd.apache.org/dev/dist</li>
  -<li>Email dev@httpd.apache.org, current-testers@httpd.apache.org, stable-testers@httpd.apache.org
to inform them of the release.</li>
  +minotaur:/www/httpd.apache.org/dev/dist</li>
  +<li>Email dev@httpd.apache.org, current-testers@httpd.apache.org and
  +stable-testers@httpd.apache.org to inform them of the release.</li>
   </ul>
     </blockquote>
    </td></tr>
  
  
  
  1.3       +10 -9     httpd-site/xdocs/dev/release.xml
  
  Index: release.xml
  ===================================================================
  RCS file: /home/cvs/httpd-site/xdocs/dev/release.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- release.xml	7 Sep 2003 05:27:32 -0000	1.2
  +++ release.xml	14 Oct 2003 15:57:53 -0000	1.3
  @@ -16,8 +16,8 @@
   <section><title>Who can make a release?</title>
   <p>Technically, any one can make a release of the source code due to the
   <a href="http://www.apache.org/LICENSE.txt">Apache Software License</a>.
  -However, only members of the Apache HTTP Server Project (committers) to
  -project can make a release designated with Apache.  Other people must
  +However, only members of the Apache HTTP Server Project (committers)
  +can make a release designated with Apache.  Other people must
   call their release something other than "Apache" unless they obtain
   written permission from the Apache Software Foundation.</p>
   
  @@ -40,11 +40,11 @@
   A private release is more suitable for that.)</p>
   </section>
   
  -<section><title>Who may make a good candidate for RM?</title>
  +<section><title>Who may make a good candidate for an RM?</title>
   <p>Someone with lots of time to kill.  Being an RM is a very important job
   in our community because it takes a fair amount of time to produce a stable
   release.  If you feel lucky, a release could be distributed without testing,
  -but our experience has shown that leads to a higher number of <i>dud</i>
  +but our experience has shown that this leads to a higher number of <i>dud</i>
   releases.  In general, our experience has shown that a well-coordinated
   release fares better than non-coordinated releases.</p>
   </section>
  @@ -83,7 +83,7 @@
   <p>Committers <i>may</i> voluntarily refrain from committing patches
if
   they wish to ease the burden on the RM, but they are under
   <font color="red">no</font> obligation to do so.  This is one reason why we
  -recommend that the RM have plenty of time on their hands - they may have to
  +recommend that the RMs have plenty of time on their hands - they may have to
   deal with a rapidly changing target.  It's not an easy job.</p>
   </section>
   
  @@ -112,11 +112,12 @@
   <p>Key points:</p>
   <ul>
   <li>Ensure that the RM's PGP/GPG key is in the httpd-dist/KEYS file</li>
  -<li>Create an official APACHE_X_Y_Z tag based of the candidate tree</li>
  -<li>Run httpd-dist/tools/release.sh script</li>
  +<li>Create an official APACHE_X_Y_Z tag based on the candidate tree</li>
  +<li>Run the httpd-dist/tools/release.sh script</li>
   <li>Copy the generated release tarballs and signatures to
  -daedalus:/www/httpd.apache.org/dev/dist</li>
  -<li>Email dev@httpd.apache.org, current-testers@httpd.apache.org, stable-testers@httpd.apache.org
to inform them of the release.</li>
  +minotaur:/www/httpd.apache.org/dev/dist</li>
  +<li>Email dev@httpd.apache.org, current-testers@httpd.apache.org and
  +stable-testers@httpd.apache.org to inform them of the release.</li>
   </ul>
   </section>
   
  
  
  

Mime
View raw message