commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jsde...@apache.org
Subject cvs commit: jakarta-commons/httpclient/xdocs applications.xml releases.xml
Date Sun, 09 Feb 2003 16:17:34 GMT
jsdever     2003/02/09 08:17:34

  Modified:    httpclient/xdocs applications.xml releases.xml
  Log:
  Update the release guide, add entry to projects.
  
  Revision  Changes    Path
  1.9       +9 -1      jakarta-commons/httpclient/xdocs/applications.xml
  
  Index: applications.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/httpclient/xdocs/applications.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- applications.xml	8 Feb 2003 01:41:49 -0000	1.8
  +++ applications.xml	9 Feb 2003 16:17:34 -0000	1.9
  @@ -72,8 +72,16 @@
             Design-a-Course, a quick, easy, and inexpensive e-learning software tool allows
novice users to 
             create sophisticated web-based training (WBT) courses within minutes.
           </dd>
  +        
  +        <dt><a href="http://www.contactoffice.com/">ContactOffice</a></dt>
  +        <dd>
  +            ContactOffice is a complete groupware solution ('Virtual office') combining
mail, 
  +            calendar, storage, contacts, and more.  HttpClient is used for back-end tasks
  +            such as inter-server communication and SMS transmission.
  +        </dd>
   
         </dl>
  +
         <hr width="50%"/>
         <p>
           To have your application listed, write to
  
  
  
  1.8       +27 -34    jakarta-commons/httpclient/xdocs/releases.xml
  
  Index: releases.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/httpclient/xdocs/releases.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- releases.xml	8 Feb 2003 01:41:49 -0000	1.7
  +++ releases.xml	9 Feb 2003 16:17:34 -0000	1.8
  @@ -29,7 +29,7 @@
   
         <p>The following steps are required to create and deploy a release version
           of a Commons library package.  The <code>example text</code> consistently
  -        assumes that we are releasing version <em>1.2</em> of the <em>httpclient</em>
  +        assumes that we are releasing version <em>2.0</em> of the <em>httpclient</em>
           package.</p>
   
         <ol>
  @@ -40,21 +40,13 @@
             committers on the particular package in question (as listed in the
             <code>project.xml</code> file) are binding.<br/><br/></li>
   
  -        <li>SSH to daedalus (aka jakarta.apache.org) and create a new subdirectory
for the
  -          release you are about to create.  For example:
  -          <pre>
  -            cd /www/jakarta.apache.org/builds/jakarta-commons/release/commons-httpclient/
  -            mkdir v1.2
  -          </pre>
  -          NOTE: Make sure that the directory you create is group writable.</li>
  -
           <li>Check out and thoroughly test the package code that you plan to
             release.<br/><br/></li>
   
  -      <li>Update the project version number in the <code>build.xml</code>,

  +        <li>Update the project version number in the <code>build.xml</code>,

             <code>project.xml</code>, and the HttpMethodBase useragent string.
             There is an Ant property named <code>component.version</code> that
would be
  -          updated to <code>1.2</code>.  Check in any files you have
  +          updated to <code>2.0</code>.  Check in any files you have
             modified.<br/><br/></li>
   
           <li>In your local repository (or on cvs.apache.org) tag <strong>only</strong>
the 
  @@ -62,7 +54,7 @@
             and version number for the package you are creating.  For example,
             <pre>
               cd $JAKARTA_COMMONS_HOME/httpclient
  -            cvs tag HTTPCLIENT_1_2
  +            cvs tag HTTPCLIENT_2_0_BETA1
             </pre>
           </li>
   
  @@ -79,16 +71,24 @@
           <li>Run <code>maven site:generate</code> 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 <code>maven site:deploy</code> to deploy the site to

  -          daedalus.<br/><br/></li>
  +          satisfied run <code>maven -Dmaven.username=your.apache.id@ site:deploy</code>
  +          to deploy the site to daedalus.<br/><br/></li>
  +
  +        <li>SSH to daedalus (aka jakarta.apache.org) and create a new subdirectory
for the
  +          release you are about to create.  For example:
  +          <pre>
  +            cd /www/jakarta.apache.org/builds/jakarta-commons/release/commons-httpclient/
  +            mkdir v2.0
  +          </pre>
  +          NOTE: Make sure that the directory you create is group writable.</li>
   
           <li>Upload the binary and source distribution files to the newly created
directory
             on daedalus.
             <pre>
               cd $JAKARTA_COMMONS_HOME/httpclient/target
               scp distributions/* \
  -                your_apache_id@jakarta.apache.org: \
  -                /www/jakarta.apache.org/builds/jakarta-commons/release/commons-httpclient/v1.2/
  +            your_apache_id@jakarta.apache.org:\
  +            /www/jakarta.apache.org/builds/jakarta-commons/release/commons-httpclient/v2.0/
             </pre>
             NOTE: Make sure that the files you copy are group writable.</li>
   
  @@ -125,24 +125,15 @@
                   cd /www/jakarta.apache.org
                   cvs update index.html site
               </pre></li>
  -            <li>You can also update the API docs and Release notes link:
  -              <pre>
  -                cd /www/jakarta.apache.org/commons/httpclient
  -                rm RELEASE-NOTES.txt
  -                rm api
  -                rm -rf commons-httpclient-1.1
  -                tar zxf ../../builds/jakarta-commons/release/commons-httpclient/v1.2/commons-httpclient-1.2.tar.gz
  -                ln -s commons-httpclient-1.2/RELEASE-NOTES.txt RELEASE-NOTES.txt
  -                ln -s commons-httpclient-1.2/docs/api api
  -            </pre></li>
             </ul>
  -          <br/>
           </li>
   
  -        <li>Update the pertinent documents in the jakarta-commons/xdocs CVS and then
build the docs by running ant.  These pages will probably include components.xml and httpclient.xml.
 CVS commit, then if you have an account on daedalus, update the commons website with a cvs
udpate in /www/jakarta.apache.org/commons.<br/></li>
  +        <li>Update the pertinent documents in the jakarta-commons/xdocs CVS and then
build the 
  +          docs by running ant.  These pages will probably include components.xml and httpclient.xml.
  +          CVS commit, then if you have an account on daedalus, update the commons website
with a 
  +          cvs udpate in /www/jakarta.apache.org/commons.<br/></li>
   
  -        <li>Announce the availability of the new package on (at least) the
  -          following mailing lists:
  +        <li>Announce the availability of the new package on the following mailing
lists:
             <ul>
               <li>announcements@jakarta.apache.org</li>
               <li>commons-dev@jakarta.apache.org</li>
  @@ -150,8 +141,8 @@
               <li>commons-httpclient-dev@jakarta.apache.org</li>
           </ul><br/></li>
   
  -        <li>Ensure that the pertinent documents in the component's home directory
are updated to reflect the new release.
  -          In particular :
  +        <li>Ensure that the pertinent documents in the component's home directory
are updated 
  +          to reflect the new release.  In particular :
             <ul>
               <li>In <strong>status.xml</strong>:
                 <ul>
  @@ -163,7 +154,9 @@
               <li>Update build with new current version</li>
             </ul>
             <br/></li>
  -        <li>Check in bugzilla for all bugs which have been marked <code>LATER</code>
and update their status appropriately. If you need to have some changes made to bugzilla you
can contact <a href="mailto:mvdb@apache.org">mvdb@apache.org</a><br/><br/></li>
  +        <li>Check in bugzilla for all bugs which have been marked <code>LATER</code>

  +          and update their status appropriately. If you need to have some changes made

  +          to bugzilla you can contact <a href="mailto:mvdb@apache.org">mvdb@apache.org</a><br/><br/></li>
   
           <li>Deploy the jar file to the ibiblio repository.
             <ul>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message