commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Caswell" <ste...@caswell.name>
Subject RE: [Lang] Release 1.1? [wasRe: [Lang] Please fix this]
Date Fri, 08 Nov 2002 21:01:48 GMT
+1 for choice #2


Steven Caswell
steven@caswell.name
a.k.a Mungo Knotwise of Michel Delving
"One ring to rule them all, one ring to find them..."


> -----Original Message-----
> From: Henri Yandell [mailto:bayard@generationjava.com] 
> Sent: Friday, November 08, 2002 10:49 AM
> To: Jakarta Commons Developers List
> Subject: Re: [Lang] Release 1.1? [wasRe: [Lang] Please fix this]
> 
> 
> 
> They seem to be the choices.
> 
> We have:
> 
> 1)
> 1.0.1 release asap. This includes the NumericRange bugfix and 
> any other bugfixes that can be dredged together. A branch 
> would be made of tag LANG_1_0 and the bugfixes retroactively applied.
> 
> 2)
> 
> 1.1 release in slightly more time. We look to make a release 
> with new functionality. We ignore certain elements if they 
> are not wanting to go out, ie) functor/reflect, but 
> everything else goes out.
> 
> 
> Postives for 1) are, we get it out quicker, but it's a lot 
> more fiddly and involves a fair amount of time.
> 
> Positives for 2) are, we continue our desire to release 
> often, and we get other fixes out etc. Rather than fiddling 
> around branching we spend time learning our process for a 2nd 
> release [ie) a lot of the 1.0 release things were special as 
> they were the first time].
> 
> 
> I'm +1 for 2).
> 
> Hen
> 
> 
> 
> 
> On Fri, 8 Nov 2002 scolebourne@btopenworld.com wrote:
> 
> > I would support a release (1.1 or 1.0.1?)....
> >
> > I haven't yet had a chance to review the functor package now its in 
> > [lang] (I'm away from home on business ATM).
> >
> > ClassUtils, ArrayUtils and all of the reflect package should be 
> > excluded at present.
> >
> > A few other bugs have been sorted too. It would be good to 
> see a list 
> > of changes from 1.0.
> >
> > IMHO, we should wait a week or so to allow more chance to look at 
> > functor, and then make a 1.1 release if its all OK.
> >
> > Stephen
> >
> >
> > >  from:    robert burrell donkin 
> <robertburrelldonkin@blueyonder.co.uk>
> > >  date:    Thu, 07 Nov 2002 20:08:09
> > >  to:      commons-dev@jakarta.apache.org
> > >  subject: Re: [Lang] Please fix this
> > >
> > > i feel very strongly that the code in reflect is not ready to be 
> > > released.
> > >
> > > in particular, i would not like to see the current method 
> names and 
> > > structure become fixed by future requirements for backwards 
> > > compatibility
> > > (just) yet.
> > >
> > > (gorden bennett! i've only made one commit and i'm 
> already sounding 
> > > like i own the shop ;)
> > >
> > > - robert
> > >
> > > On Thursday, November 7, 2002, at 07:15 PM, Steve Downey wrote:
> > >
> > > > I agree that CVS head is not in a releaseable state. 
> But the bug 
> > > > is fairly compelling. I think releasing off a branch from the 
> > > > release tag is the best solution.
> > > >
> > > > On Thursday 07 November 2002 12:05 pm, Henri Yandell wrote:
> > > >> Fixed in CVS, so will be in the nightly build tonight 
> at the very 
> > > >> least. And UnitTest made so Max and Min are being tested.
> > > >>
> > > >> Any views out there on the merits of a release?
> > > >>
> > > >> My judgement is that the current CVS tree is not 
> releasable, so 
> > > >> it would be a question of releasing against the tag.
> > > >>
> > > >> Any other bugs that should be included?
> > > >>
> > > >> Hen
> > > >>
> > > >> On Thu, 7 Nov 2002, [ISO-8859-1] Kasper Rönning wrote:
> > > >>> Quite a bug in Commons-Lang: class NumberRange, method 
> > > >>> geMaximum() returns minimum. Could you make a new release?
> > > >>>
> > > >>> /Kasper Ronning
> > > >>>
> > > >>>
> > > >>> --
> > > >>> To unsubscribe, e-mail: 
> > > >>> <mailto:commons-dev-unsubscribe@jakarta.apache.org> For

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



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


Mime
View raw message