Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jakarta-httpclient 
Wiki" for change notification.

The following page has been changed by MichaelBecke:
http://wiki.apache.org/jakarta-httpclient/HttpClientReleaseProcess

------------------------------------------------------------------------------
- '''This document is still in progress'''
- 
- The following steps are required to create and deploy a release version of a 
Commons library package. The example text consistently assumes that we are 
releasing version 3.0.1 of the httpclient  package.
+ The following steps are required to create and deploy a release version of 
the HttpClient library package. The example text consistently assumes that we 
are releasing version 3.0.1 of the package.
  
  == Pre Release ==
  
-    * Announce your proposed release of a particular package to the 
httpclient-dev@jakarta.apache.org mailing list, and ask for a vote. Per the 
Jakarta Project charter, votes of committers on the particular package in 
question (as listed in the project.xml file) are binding.
+    * Announce your proposed release to the httpclient-dev@jakarta.apache.org 
mailing list, and ask for a vote. Per the Jakarta Project charter, votes of 
committers on the particular package in question (as listed in the project.xml 
file) are binding.
  
     * Assuming the vote is successful send an email to 
httpclient-dev@jakarta.apache.org and [EMAIL PROTECTED] with the outcome of the 
vote.  Something like the following:
  {{{
@@ -83, +81 @@

  == Publishing the Release ==
  
     * Copy binary and source distributions into the HttpClient dist 
directory.{{{
-    set DIST_DIR=/www/www.apache.org/dist/jakarta/commons/httpclient
+    export DIST_DIR=/www/www.apache.org/dist/jakarta/commons/httpclient
-    cp commons-httpclient-3.0.1-src* $DIST_DIR/source
+    cp commons-httpclient-3.0.1-src* $DIST_DIR/source/
-    cp commons-httpclient-3.0.1.tar* commons-httpclient-3.0.1.zip* 
$DIST_DIR/binary
+    cp commons-httpclient-3.0.1.tar* commons-httpclient-3.0.1.zip* 
$DIST_DIR/binary/
     cp release-notes.txt $DIST_DIR/RELEASE_NOTES.txt}}}
     * Copy the jar and POM to the ibiblio dist directory. {{{
-    set IBIBLIO_DIR=/www/www.apache.org/dist/java-repository/commons-httpclient
+    export 
IBIBLIO_DIR=/www/www.apache.org/dist/java-repository/commons-httpclient
-    cp commons-httpclient-3.0.1.jar* $IBIBLIO_DIR/jars
+    cp commons-httpclient-3.0.1.jar* $IBIBLIO_DIR/jars/
     cp project.xml $IBIBLIO_DIR/poms/commons-httpclient-3.0.1.pom}}}
     * Be sure that all files belong to the ''jakarta'' group and that they are 
group writable.
  
  === Updating the Jakarta website ===
  
+   * Check out the [https://svn.apache.org/repos/asf/jakarta/site jakarta 
site] directory from SVN.
+   * Update ''news.xml'' and ''xdocs/downloads/downloads.xml'' to.
+   * Run ''ant'' from the site directory to regenerate the site docs.
+   * Checkin the modified docs.
+    `svn commit -m "Updates for the HttpClient 3.0.1 release"`
+   * From ''people.apache.org'' update the Jakarta site.
+    {{{
+    cd /www/jakarta.apache.org/site
+    svn update}}}
  
-    1. Create a news item. This should be added to httpclient/xdocs/news.xml 
and the jakarta-site2/xdocs/site/news.xml as well as a one liner in 
jakarta-site2/xdocs/index.html
+ === Redeploy the HttpClient site ===
  
-    1. Run maven site:generate to generate the website documentation. Browse 
the generated docs in the target directory to ensure that they are correct and 
complete. Modify the xdocs as required and when satisfied run maven 
-Dmaven.username=your.apache.id@ site:deploy to deploy the site to daedalus.
+   {{{maven -Dmaven.username=mbecke site:deploy}}}
  
-    1. SSH to daedalus (aka jakarta.apache.org) and create a new subdirectory 
for the release you are about to create. For example:
+ == Accounce the release ==
  
-                   cd 
/www/jakarta.apache.org/builds/jakarta-commons/release/commons-httpclient/
-                   mkdir v2.0
-                 
+   * Send an email announcing the release to the following lists:
+    * announcements@jakarta.apache.org
+    * httpclient-dev@jakarta.apache.org
+    * httpclient-user@jakarta.apache.org
+    * [EMAIL PROTECTED]
+   * The email should look something like the following: {{{
+ Subject: [ANNOUNCEMENT] Commons HttpClient 3.0.1 Released
  
-       NOTE: Make sure that the directory you create is group writable.
-   1. Upload the binary and source distribution files to the newly created 
directory on daedalus.
+ The Jakarta Commons HttpClient project is pleased to announce the
+ release of HttpClient 3.0.1. This version fixes a number of bugs found since 
+ the release of 3.0. All HttpClient users are encouraged to upgrade.  Please 
+ download and enjoy.
  
-                   scp target/distributions/* \
-                   [EMAIL PROTECTED]:\
-                   
/www/jakarta.apache.org/builds/jakarta-commons/release/commons-httpclient/v2.0/
-                 
+ Download - 
<http://jakarta.apache.org/site/downloads/downloads_commons-httpclient.cgi>
+ Release notes -
+ <http://www.apache.org/dist/jakarta/commons/httpclient/RELEASE-NOTES.txt>
+ HttpClient site - <http://jakarta.apache.org/commons/httpclient/>
  
-       NOTE: Make sure that the files you copy are group writable.
-   1. The release packages must also be uploaded to www.apache.org which is 
also hosted by daedalus.
+ About HttpClient -
+ Although the java.net package provides basic functionality for
+ accessing resources via HTTP, it doesn't provide the full flexibility
+ or functionality needed by many applications. The Jakarta Commons
+ HttpClient component seeks to fill this void by providing an
+ efficient, up-to-date, and feature-rich package implementing the
+ client side of the most recent HTTP standards and recommendations.
  
+ Enjoy,
-                   scp target/distributions/commons-httpclient-2.0-src.* \
-                     [EMAIL PROTECTED]:\
-                     /www/www.apache.org/dist/jakarta/commons/httpclient/source
-                   scp target/distributions/commons-httpclient-2.0.* \
-                     [EMAIL PROTECTED]:\
-                     /www/www.apache.org/dist/jakarta/commons/httpclient/binary
-                 
  
+ Commons HttpClient Team
+ }}}
-       NOTE: Make sure that the files you copy are group writable.
-   1. Follow standard procedures to update the Jakarta web site (stored in CVS 
repository jakarta-site2 to reflect the availability of the new release. 
Generally, you will be updating the following pages:
-           * xdocs/site/binindex.xml - Create a link to the release directory 
under the Release Builds heading.
-           * xdocs/site/sourceindex.xml - Create a link to the release 
directory under the Release Builds heading.
-           * xdocs/site/news.xml - Create a news item that describes the new 
release, and includes hyperlinks to the release directory.
-           * xdocs/index.xml - Create a one line news item that links to the 
full item in site/news.xml.
-           * Then run ant at the base to generate the new docs and commit the 
changes to jakarta-site2. You will be committing the updated xdocs and html.
  
-                             ant
-                             cvs commit -m "update to reflect release of 
commons-httpclient"
-                         
- 
-           * If you have an account on daedalus, log in and update the web 
site:
- 
-                             cd /www/jakarta.apache.org
-                             cvs update index.html site
-                         
- 
-   * Announce the availability of the new package on the following mailing 
lists:
-           * announcements@jakarta.apache.org
-           * commons-dev@jakarta.apache.org
-           * commons-user@jakarta.apache.org
-           * commons-httpclient-dev@jakarta.apache.org
- 
-   * Deploy the jar file to the ibiblio repository.
- 
-                   maven jar:deploy
-                 
- 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to