You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by sk...@apache.org on 2005/06/13 13:12:40 UTC
svn commit: r190383 -
/jakarta/commons/proper/commons-build/trunk/xdocs/releases/release.xml
Author: skitching
Date: Mon Jun 13 04:12:38 2005
New Revision: 190383
URL: http://svn.apache.org/viewcvs?rev=190383&view=rev
Log:
Minor improvements to release procedure notes.
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?rev=190383&r1=190382&r2=190383&view=diff
==============================================================================
--- jakarta/commons/proper/commons-build/trunk/xdocs/releases/release.xml (original)
+++ jakarta/commons/proper/commons-build/trunk/xdocs/releases/release.xml Mon Jun 13 04:12:38 2005
@@ -329,6 +329,21 @@
mv ~/release/RELEASE-NOTES.txt .
</pre>
</p>
+ <p>
+ <strong>Remove Obsolete Releases</strong><br/>
+ If there are releases in the binary or source directory that are not expected to
+ be frequently accessed (eg releases more than 2 years old) then these files should
+ be deleted; this will cause the files to also be deleted from the mirrors and
+ save them some diskspace as well as simplifying things for users. Note that the
+ contents of the /www/www.apache.org/dist directory is regularly copied to
+ /www/archive.apache.org/dist and from there transferred to host archive.apache.org.
+ Deleting files from the standard distribution directories does <i>not</i> delete
+ them from the archive dist directories (this is a copy, not an rsync) so users will
+ still be able to access old files even when they are not available from the mirrors.
+ The automatic transfer of files to the archive directory also means that you do not
+ need to take any special actions to ensure your new files are made available on
+ archive.apache.org.
+ </p>
</subsection>
<subsection name='8 Deploy jar, project.xml and license.html to Java-Repository'>
@@ -409,7 +424,9 @@
</p>
<p>
Note that the files are transferred to the real jakarta web server only every
- few hours, so it may be a while before you see your changes appear.
+ few hours, so it may be a while before you see your changes appear. However if
+ you set your webbrowser's HTTP proxy to 209.237.227.195 port 80 and access
+ http://jakarta.apache.org/ you should be able to see the changes immediately.
</p>
<strong>Perform Manual Fixups (if any)</strong>
<p>
@@ -468,13 +485,16 @@
<p>
Note that in order to commit changes to the site directory you must be in subversion
group "jakarta-site". If you are a member of the Jakarta PMC, then just ask on
- the pmc@jakarta.apache.org mailing list. If you are not a PMC member, then post the diff
- to general@jakarta.apache.org and ask for someone to complete this step for you.
- Note that currently after someone has been added to the "jakarta-site" access list in file
- https://svn.apache.org/repos/asf/infrastructure/trunk/subversion/authorization/asf-authorization,
- a member of the infrastructure team still has to manually run "svn update" to update the
- actual subversion authorization file (/x1/svn/asf-authorization); this will hopefully be
- automated sometime in 2005.
+ the pmc@jakarta.apache.org mailing list for access; this can be granted by editing
+ the file
+ <pre>
+ https://svn.apache.org/repos/asf/infrastructure/trunk/subversion/authorization/asf-authorization
+ </pre>
+ to add your userid to the jakarta-site group.
+ </p>
+ <p>
+ If you are not a PMC member, then post the diff to general@jakarta.apache.org and ask for
+ someone to commit these changes for you.
</p>
<p>
See the README.txt file in the subversion site directory for more information on how to
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org