Re: [lang] 2.0 release - again

[Stephen Colebourne <sc...@btopenworld.com>]

I have checked the zips and they look fine. It must be time to upload the
release isn't it? Haven't we received word that the servers are clear now?

For 2.1 we could add some TODOs:
- Better overview.html
- Better package.html for main lang package
- Better class-level javadoc for BitField

Stephen

----- Original Message -----
From: "Henri Yandell" <ba...@generationjava.com>
> New binary, source, docs/ and JDiff changes uploaded to:
>
> http://www.apache.org/~bayard/commons-lang-2.0/
>
> Not bothering with the Maven build at the moment.
>
> Hen
>
> On Wed, 27 Aug 2003, Henri Yandell wrote:
>
> >
> >
> > On Tue, 26 Aug 2003, Phil Steitz wrote:
> >
> > >
> > > --- Henri Yandell <ba...@generationjava.com> wrote:
> > > >
> > > > First, let's make sure we keep the subjects on topic, and keep the
[lang]
> > > > there for anything other than a [VOTE].
> > > >
> > > > Second, shall I tag the current changes to builder/ and lang/
changes.
> > > > Unsure if it was all just javadoc chances. Guess I should dig
through a
> > > > changelog :) Assuming I do, should I go ahead and tag these to 2.0?
> > >
> > > +1
> >
> > I've built a Changelog with tags, gone over it and nothing has been
added
> > which is not a javadoc change [at least according to the cvs comments].
> >
> > I've tagged the new files with LANG_2_0, and this tag is intended to be
> > the one for Lang 2.0. I'm not expecting any other changes to go into
this.
> > [It builds into the distribution files happily, though I've not pushed
> > them up yet to my home dir].
> >
> > The Daedalus to Minotaur migration appears to be getting close to
> > finished, if not completely finished, so we can think about doing a
> > release [and before that another vote].
> >
> > I think people can start working on Lang 2.1/3.0 now as well. If any
> > important changes have to happen to 2.0, I can branch off and make the
> > changes for a release there.
> >
> > 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
>