Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Message-ID: <245A7290F0E0D311BF6E009027E7908B072047C4@atlanta.seagullsw.com>
From: Gary Gregory <ggregory@seagullsw.com>
To: 'Jakarta Commons Developers List' <commons-dev@jakarta.apache.org>
Subject: RE: [lang] Lang 2.0 release?
Date: Thu, 21 Aug 2003 00:22:55 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3679B.E5099C70"

------_=_NextPart_001_01C3679B.E5099C70
Content-Type: text/plain

Inline...

> -----Original Message-----
> From: Henri Yandell [mailto:bayard@generationjava.com]
> Sent: Wednesday, August 20, 2003 20:44
> To: Jakarta Commons Developers List
> Subject: RE: [lang] Lang 2.0 release?
> 
> 
> 
> On Wed, 20 Aug 2003, Gary Gregory wrote:
> 
> > This is all good news. I have two Q's:
> >
> > (1) What about an RC-4 that is publicized to the commons-user list such
> that
> > real users can raise issues such that we can:
> >
> > 	(a) document them in a migration doc or
> > 	(b) fix them.
> 
> Dunno. Do we want users to be using RCs? I think I'd prefer to have them
> use the x.0 and release an x.0.1 for any issues etc.

Well, the changes that we have been going through, moving classes, removing
code, etc, have been pretty radical from beta to beta and from RC to RC. I
guess it is matter of expectations from the user base. I does sound, that
now, right now, we have a stable build. I think it is a bit odd to release a
2.0 release with the explicit understanding that the user base should wait
until a 2.0.1 to become the real stable release. Furthermore, what if, in
theory, the changes asked by users to 2.0 would really not be backwards
compatible with 2.0, therefore needing to call the next release a 2.1? Kind
of odd to have a super short lived 2.0. All of my ramblings to say that it
does not quite feel right to me to push a release out without a
beta/rc/feedback cycle from *some* users.

> 
> > (2) It's seems trivial to add the missing @since tags JDiff complains
> about.
> > Or that just too anal?
> 
> S'not too hard to remove the tag and redo the build. Feel free to commit
> them :)

I'll see if I can get some in there...

> 
> Hen
> 
> >
> > Gary
> >
> > > -----Original Message-----
> > > From: Henri Yandell [mailto:bayard@generationjava.com]
> > > Sent: Wednesday, August 20, 2003 20:01
> > > To: Jakarta Commons Developers List
> > > Subject: [lang] Lang 2.0 release?
> > >
> > >
> > > Seems that since RC3, we've just:
> > >
> > > removed an unused private attribute
> > > updated javadoc in a few places
> > > removed a method
> > > moved 2 classes up a package from util
> > > removed a class from util
> > >
> > > While I could build an RC4, I'm going to be hopeful and build a
> release
> > > build. CVS tags can always be deleted/moved in case of major issues
> > > again.
> > >
> > > If no one can find a problem by tomorrow morning, I'll call a vote on
> > > Commons-dev, Ccing the PMC. Assuming things go well, we ought to get 3
> > > non-Lang +1's by the weekend.
> > >
> > > I'll aim to do the release stuff over the weekend [mirrors will be new
> to
> > > me] and have the release on the site by the end of the weekend, which
> > > always seems to be good timing.
> > >
> > > Any thoughts?
> > >
> > > Release build in:
> > >
> > > http://www.apache.org/~bayard/commons-lang-2.0/
> > >
> > > Also, the following file from JDiff is very useful, I hadn't noticed
> it
> > > before:
> > >
> > > http://www.apache.org/~bayard/commons-lang-2.0/Commons-Lang-1.0.1-to-
> > > 2.0/missingSinces.txt
> > >
> > > [although hopefully it's something we can leave to fix until 2.1]
> > >
> > > Hen
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org

------_=_NextPart_001_01C3679B.E5099C70--