httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rpl...@apache.org
Subject svn commit: r495422 - in /httpd/site/trunk: docs/dev/release.html xdocs/dev/release.xml
Date Thu, 11 Jan 2007 22:48:48 GMT
Author: rpluem
Date: Thu Jan 11 14:48:47 2007
New Revision: 495422

URL: http://svn.apache.org/viewvc?view=rev&rev=495422
Log:
* - Clarified location of release.sh script
  - minotaur is an internal server name. Replaced it with people.apache.org
  - Added a reminder to add the new release to Bugzilla

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

Modified: httpd/site/trunk/docs/dev/release.html
URL: http://svn.apache.org/viewvc/httpd/site/trunk/docs/dev/release.html?view=diff&rev=495422&r1=495421&r2=495422
==============================================================================
--- httpd/site/trunk/docs/dev/release.html (original)
+++ httpd/site/trunk/docs/dev/release.html Thu Jan 11 14:48:47 2007
@@ -230,9 +230,9 @@
 <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 on the candidate tree</li>
-<li>Run the httpd-dist/tools/release.sh script</li>
+<li>Run the httpd/site/trunk/dist/tools/release.sh script</li>
 <li>Copy the generated release tarballs and signatures to
-minotaur:/www/httpd.apache.org/dev/dist</li>
+people.apache.org:/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>
@@ -301,13 +301,16 @@
   <blockquote>
 <p>Once the release has reached the highest-available designation (as deemed
 by the RM), the release can be moved to the httpd distribution directory
-on apache.org.  Approximately 24 to 48 hours after the files have been moved,
-a public announcement can be made.  We wait this period so that the mirrors
-can receive the new release before the announcement.  An email can then be
-sent to the announcements lists (announce@apache.org,
-announce@httpd.apache.org).  Drafts of the announcement are usually
-posted on the development list before sending the announcement to let the
-community clarify any issues that we feel should be addressed in the
+on apache.org.  It should be ensured that the release is also added to
+Bugzilla by sending a mail to dev@httpd.apache.org requesting the same.  The
+request is picked up there by one of the project members with Bugzilla
+administrator permissions and the release is added to Bugzilla.  Approximately
+24 to 48 hours after the files have been moved, a public announcement can be
+made.  We wait this period so that the mirrors can receive the new release
+before the announcement.  An email can then be sent to the announcements lists
+(announce@apache.org, announce@httpd.apache.org).  Drafts of the announcement
+are usually posted on the development list before sending the announcement to
+let the community clarify any issues that we feel should be addressed in the
 announcement.</p>
   </blockquote>
  </td></tr>

Modified: httpd/site/trunk/xdocs/dev/release.xml
URL: http://svn.apache.org/viewvc/httpd/site/trunk/xdocs/dev/release.xml?view=diff&rev=495422&r1=495421&r2=495422
==============================================================================
--- httpd/site/trunk/xdocs/dev/release.xml (original)
+++ httpd/site/trunk/xdocs/dev/release.xml Thu Jan 11 14:48:47 2007
@@ -113,9 +113,9 @@
 <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 on the candidate tree</li>
-<li>Run the httpd-dist/tools/release.sh script</li>
+<li>Run the httpd/site/trunk/dist/tools/release.sh script</li>
 <li>Copy the generated release tarballs and signatures to
-minotaur:/www/httpd.apache.org/dev/dist</li>
+people.apache.org:/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>
@@ -165,13 +165,16 @@
 <section><title>How do we make it public?</title>
 <p>Once the release has reached the highest-available designation (as deemed
 by the RM), the release can be moved to the httpd distribution directory
-on apache.org.  Approximately 24 to 48 hours after the files have been moved,
-a public announcement can be made.  We wait this period so that the mirrors
-can receive the new release before the announcement.  An email can then be
-sent to the announcements lists (announce@apache.org,
-announce@httpd.apache.org).  Drafts of the announcement are usually
-posted on the development list before sending the announcement to let the
-community clarify any issues that we feel should be addressed in the
+on apache.org.  It should be ensured that the release is also added to
+Bugzilla by sending a mail to dev@httpd.apache.org requesting the same.  The
+request is picked up there by one of the project members with Bugzilla
+administrator permissions and the release is added to Bugzilla.  Approximately
+24 to 48 hours after the files have been moved, a public announcement can be
+made.  We wait this period so that the mirrors can receive the new release
+before the announcement.  An email can then be sent to the announcements lists
+(announce@apache.org, announce@httpd.apache.org).  Drafts of the announcement
+are usually posted on the development list before sending the announcement to
+let the community clarify any issues that we feel should be addressed in the
 announcement.</p>
 </section>
 



Mime
View raw message