Re: alpha3 release candidate 2 ready

[Jeffrey Dever]

I was quite casual with the initial builds as this was using a different 
build procedure than before (ant based as opposed to maven based).  I 
was not very confident initially, which is why I did not tag the 
repository and was calling the builds release candidates, which I 
wouldn't normally do for an alpha.

I agree with your reccomended procedure, which is indeed what I did for 
the last build.  I will endevour to be more rigorus as we get into beta 
and then actual release candidates and builds.

Martin Cooper wrote:

Allow me to clarify.

Procedure as I perceive it, per the left over files:
* Make final changes to code for release, in local work tree.
* Commit all changes.
* Tag CVS for the release.
* Build the distribution from the local work tree.
Recommended procedure:
* Make final changes to code for release, in local work tree.
* Commit all changes.
* Tag CVS for the release.
* Check out a completely new clean tree based on the CVS tag created in
previous step.
* Build the distribution from this new clean tree.
The second approach has several advantages:

1) If you have forgotten to tag something in the tree, you will be
forcefully reminded, because the attempt to build the distribution will
fail.
2) Left-over files in a local work tree will not find their way into the
distribution.
3) You ensure that someone who decides to build the release from CVS can do
so successfully by simply retrieving the source based on the correct tag.
This is the approach I use for releasing Struts, Commons FileUpload and
Commons Validator.
--
Martin Cooper
 

-----Original Message-----
From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED]
Sent: Monday, February 24, 2003 11:36 AM
To: Commons HttpClient Project
Subject: RE: alpha3 release candidate 2 ready
Martin
That's the way things are done in all Jakarta sub-projects. I 
am afraid
we have to conform
Cheers
Oleg

On Mon, 2003-02-24 at 20:12, Martin Cooper wrote:
   

-----Original Message-----
From: Michael Becke [mailto:[EMAIL PROTECTED]
Sent: Monday, February 24, 2003 8:05 AM
To: Commons HttpClient Project
Subject: Re: alpha3 release candidate 2 ready
There are a few extra files in the src directory:

MultiThreadedHttpConnectionManager.java.orig
TestHttpConnectionManager.java.orig
TestHttpConnectionManager.java.rej
src/java/org/apache/commons/httpclient/log/
       

I could easily be wrong, since I'm not too familiar with 
     

the HttpClient
   

build process, but this looks like the result of building 
     

from a local work
   

tree, rather than from a tree obtained fresh from CVS using 
     

the relevant
   

tag. If so, I'd like to suggest the latter, since it's more 
     

reliable, and
   

ensures that everything necessary is tagged in CVS.

--
Martin Cooper
     

Other than these it looks good to go.

Mike

Jeffrey Dever wrote:
       

Ok, new rc2 package available:

         

http://jakarta.apache.org/builds/jakarta-commons/release/commo
ns-httpclient/v2.0 
       

Michael Becke wrote:

         

If we are only going to release one file I would suggest 
           

using zip  
       

instead of tar.gz.

Mike

On Monday, February 24, 2003, at 02:10 AM, Jeffrey Dever wrote:

           

I just put up a release candidate for alpha3:

             

http://jakarta.apache.org/builds/jakarta-commons/release/commons- 
   

httpclient/v2.0

It was build with the ant task instead of maven this 
             

time.  I made a  
       

few tiny changes that have not been checked in to cvs 
             

yet, and  
   

repository has not been labeled.  If we vote this as OK 
             

I'll just  
       

rename it.

Please check it out.

Jandalf.



             

---------------------------------------------------------------------
   

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

             

           

---------------------------------------------------------------------
   

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

           



         

---------------------------------------------------------------------
   

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

         

       

---------------------------------------------------------------------
   

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

       

     

---------------------------------------------------------------------
   

To unsubscribe, e-mail: 
     

[EMAIL PROTECTED]
   

For additional commands, e-mail: 
     

[EMAIL PROTECTED]
   

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

   



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



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