+1

> -----Original Message-----
> From: Morgan Delagrange [mailto:[EMAIL PROTECTED]] 
> Sent: Wednesday, February 20, 2002 9:28 AM
> To: Morgan Delagrange; Jakarta Commons Developers
> Subject: Re: [COLLECTIONS] [VOTE] Begin official preparation 
> for Collections 2.0
> 
> 
> So, since there appears to be a swell of implied support for 
> Collections 2.0, and no dissenters, I'm going to go ahead and 
> move 1.x off to a branch, despite the lack of three +1 votes. 
>  :)  Sorry to skip the technicality, I just have the new 
> LRUMap class that I'd like to check in.
> 
> - Morgan
> 
> ----- Original Message -----
> From: "Morgan Delagrange" <[EMAIL PROTECTED]>
> To: "Jakarta Commons Developers" <[EMAIL PROTECTED]>
> Sent: Tuesday, February 19, 2002 3:50 PM
> Subject: [COLLECTIONS] [VOTE] Begin official preparation for 
> Collections 2.0
> 
> 
> > Hi all,
> >
> > Before I check in classes that totally break 1.x compatibility, I 
> > think I should create a branch in CVS for future 1.x 
> version(s) (bug 
> > fixes and such).  This was actually included in the original 
> > HOWTO-RELEASE document
> in
> > Taglibs, but somehow it never made it into the Commons 
> version.  I've
> quoted
> > the relevant portion from Taglibs at the end of this email.
> >
> > So, I propose that we copy the current HEAD version of 
> Collections to 
> > a branch called "collections-1.x" (or something similar) in 
> > preparation for additional 2.0 activity.
> >
> > - Morgan
> >
> >
> > FROM TAGLIBS HOWTO-RELESE
> > ----------------------------------------------
> > 3 STARTING/COMPLETING MAJOR RELEASES
> >
> > (See section 1.1 for the definition of a "Major" release.)  Let's 
> > assume that the current release of your tag library is 
> 2.0.4, but you 
> > want to start
> work
> > on 3.0.  Here are the steps you would take to start working 
> on the new
> > release:
> >
> >   1) Make an announcement on taglibs-dev
> >   2) Create a branch called rel2 in CVS for the entire tag library,
> >      which will preserve the currently released version
> >   3) Continue work for the 3.0 release on the MAIN branch
> >
> > Once the 3.0 version is ready for release to the public, 
> you would do
> this:
> >
> >   1) Call a release vote on taglibs-dev
> >   2) After receiving approval, build the release jar and 
> place it on 
> > the site
> >
> > The version 3 release is the main trunk of the CVS tree.  However,
> versions
> > 2 and 1 will still be available on other branches (rel2 and 
> rel1), if
> other
> > releases of that version prove necessary.
> >
> >
> 
> 
> 
> _________________________________________________________
> 
> Do You Yahoo!?
> 
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:commons-dev-> [EMAIL PROTECTED]>
> For 
> additional commands, 
> e-mail: <mailto:[EMAIL PROTECTED]>
> 
> 

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

Reply via email to