[lang] beta release

[Henri Yandell <ba...@generationjava.com>]

One of my suggestions during the discussions prior to the migration was a
timeline. Part of that suggestion was the release of a beta release so
that there is a jar available for people currently using Commons.Lang that
is considered stable.

It also gives us the opportunity to build up a simple website around it
and move it on to the release level.

Does anyone have any opinions on the beta release?

*) Should it be done?

*) Are we ready for a beta?

The beta idea is based upon the Versioning page on the Commons site where
it states a reason for a beta as "Generating a stable version before
large-scale changes", where the large-scale changes are intended to be new
classes and functionality but not changes to the functionality of any
existing methods in the current version of Lang [my view].

Hen

**************

[the timeline suggestion, I thought it could be done by early August, but
 there's no need to rush, depends all on the new features. ]

[Tuesday 16th July]
Tonight: Vote for Commons Proper.
Thursday: Migrate to Commons Proper. Release of beta.
Friday: Begin discussion of the 4 or 5 new areas with a focus of closing
each one off within a week.
Weekend/Monday: Begin work on a site and all the necessary admin such as
deployment to Maven, checking on gump etc.

later: All submissions decided upon, submission freeze.
later++: Code/UnitTests should be complete.
later++: Vote on release.



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: [lang] beta release

[Henri Yandell <ba...@generationjava.com>]

On Fri, 19 Jul 2002, [iso-8859-1] Ringo De Smet wrote:

> > Friday: Begin discussion of the 4 or 5 new areas with a focus of
> > closing each one off within a week.
>
> What areas are still under discussion? I think that we need a concensus
> first on these areas before we are ready for a beta release.

The areas for discussion are new submissions which would not be expected
to change the current code's API, merely add to it. Thus I was thinking of
a beta release with the current functionality, and then the discussion and
migration of the various submissions.

I'll start a thread on each submission [unless people beat me to it]
today/this weekend.

Hen


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: [lang] beta release

[Ringo De Smet <ri...@yahoo.co.uk>]

 --- Henri Yandell <ba...@generationjava.com> wrote: 
> Does anyone have any opinions on the beta release?
> 
> *) Should it be done?

Yes.

> *) Are we ready for a beta?

See below.

> Friday: Begin discussion of the 4 or 5 new areas with a focus of
> closing each one off within a week.

What areas are still under discussion? I think that we need a concensus
first on these areas before we are ready for a beta release.

Start up the discussions! :)

Ringo

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>