Hello, as a potential user, I'd suggest you go with an alpha. It would convey the message that there will probably be some more API change, albeit not many. To me beta suggest that the API is set and only bugs that won't change the API will be fixed.
Anyway, looking forward to start using it, whatever you decide. SaM On Wed, Jun 30, 2010 at 9:43 AM, Henri Yandell <flame...@gmail.com> wrote: > Here are example tarballs, jar and a site for a 3.0 beta: > > http://people.apache.org/~bayard/commons-lang-3.0-beta/ > > The site isn't intended to be ready - that can be done later. What it > does right now is provide the relevant 3.0 reports. > > What I'd like to know right now is if it looks good and whether I > should go ahead and tag 3.0-beta and do a real release build. I think > we're ready to build a beta. I don't expect a lot of API change after > this, and I don't know of any bugs in 3.0 that weren't in 2.x. > > So not a release vote, but looking for consensus from anyone (users, > committers, pmc) that it's time to put a beta stake in the ground. > > Hen > > On Mon, Jun 28, 2010 at 2:23 PM, Jörg Schaible <joerg.schai...@gmx.de> wrote: >> Honton, Charles wrote: >> >>> Be it alpha, beta, or full release: when is a version 3 of commons-lang >>> going to be available? >> >> It's probably this year. >> >> - Jörg >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
