commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <>
Subject RE: [lang] Is there a schedule?
Date Wed, 22 Jan 2003 15:42:12 GMT
Are we saying that a 1.0.2 release is not possible since the fixes are
significant and break API contracts which is why the next release /must/ be
a minor or major release /and/ that if we are talking about a major or minor
release then we must talk about (argue) new features, which is "painful"?

What about a minor (1.1) release with all bug fixes and no new feature? Then
a release for new features. Just one step at a time, splitting the arguing
b/w bug arguments and feature arguments?


-----Original Message-----
From: Stephen Colebourne []
Sent: Tuesday, January 21, 2003 3:11 PM
To: Jakarta Commons Users List
Subject: Re: [lang] Is there a schedule?

From: "Henri Yandell" <>
> On Tue, 21 Jan 2003, Gary Gregory wrote:
> > WRT Commons-Lang, I would like to get the ToStringBuilder reflection
> > for class hierarchies from a released build rather than a nightly build.
> >
> > A maintenance release would allow me to further clean up our code base
> > from our various inconsitent toString implementations and use the now
> > ToStringBuilder. I would be happy with a 1.0.x level release but I am
> > sure if this is easy to do for you guys. A 1.0.x release could simply
> > include new packages.
> +1 to a release of Commons Lang 1.0.2, with bugfixes but no new
> functionality.

-1. The changes being talked about here are definitely 1.1 if not 2.0. they
are not minor bug fixes, but major ones.


> I suspect that many of the new functionalities in the dev tree will be
> argued long and hard over.
> We also need to get the 2.0 arguments started again, but it's all getting
> quite tiring and painful.
> > What happens if a nightly build fails in a unit test? Is it not posted?
> I think so, but am not 100%.
> Hen
> --
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message