You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Henri Yandell <ba...@generationjava.com> on 2003/08/22 16:55:08 UTC
[VOTE] Release of Commons Lang 2.0 [take 2]
We've already called a vote on this back in May, but a -1 that wanted us
to include Lang.time caused us to delay and since then we've been dealing
with more minutae.
So, without further ado, I'll repeat my call for a VOTE last May. The
information on what has changed below is largely the same as it was in
May.
The largest change since May not reflected below is a big push on Unit
Tests [thanks to Clover's superb visualisation, we've got about 88%
coverage in Clover] and documentation [thanks to Maven and JDiff].
========================================================================
Our t's are dotted and our i's are crossed, so we'd like to make a
release of Commons Lang 2.0.
[ ] +1 I support Commons Lang 2.0
[ ] +0 Huh? Sure, let me sleep.
[ ] -0 Lang? Sounds bad.
[ ] -1 I hate you guys.
[http://www.apache.org/~bayard/lang2.0/ contains what I am planning to use
as the build, we will not be using Maven as the site for 2.0, but I
generate it for reference]
What's not going:
----------------
lang.functor has been removed from Lang. Collections will gain what it
needs and [Functor] will be looked to for the complete functor-style
solution.
lang.reflect is not ready yet.
lang.util.Identifier is not ready yet.
New maven configuration with the aim of moving Lang to a mavenised site.
What's new:
----------
lang.math.* package, which contains Range classes, RandomUtils and a
Fraction class.
In the top level package, we see a series of additions. There are a set of
reusable Exceptions which provide slightly tighter meaning than their
Commons Lang superclasses, IllegalClassException and
NotImplementedException are examples of these. We also see the addition of
more Utils classes:
ArrayUtils
BooleanUtils
ClassUtils
StringEscapeUtils
StringPrintWriter
WordUtils
We also see the addition of
Validate class [akin to JUnit Assert in style] and BitField from the old
Commons Util project [as created by POI].
What's changed:
--------------
ToStringBuilder has gained an inner class.
builder.* packages have gained new methods
NumberUtils has a series of constants, LONG_ZERO, LONG_ONE etc.
StringUtils has a series of new methods.
The order in which a nested exception is printed has been reversed and a
static legacy option left to reverse it the other way if desired. This
now matches JDK 1.4 direction.
What's gone:
-----------
lang.NumberRange is gone as it has now moved into the math subpackage.
The release:
-----------
Following a successful vote, the PMC will be notified of the desire to
release and the instructions at
http://jakarta.apache.org/commons/releases/ followed to create a
release. A changelog with 'jardiff' will be included and JDiff will be
used to generate a site showing changes [as shown in
http://www.apache.org/~bayard/commons-lang-2.0/Commons-Lang-1.0.1-to-2.0/changes.html].
Hen
Re: [VOTE] Release of Commons Lang 2.0 [take 2]
Posted by Phil Steitz <ph...@steitz.com>.
Henri Yandell wrote:
> We've already called a vote on this back in May, but a -1 that wanted us
> to include Lang.time caused us to delay and since then we've been dealing
> with more minutae.
>
> So, without further ado, I'll repeat my call for a VOTE last May. The
> information on what has changed below is largely the same as it was in
> May.
>
> The largest change since May not reflected below is a big push on Unit
> Tests [thanks to Clover's superb visualisation, we've got about 88%
> coverage in Clover] and documentation [thanks to Maven and JDiff].
>
> ========================================================================
>
> Our t's are dotted and our i's are crossed, so we'd like to make a
> release of Commons Lang 2.0.
>
> [X] +1 I support Commons Lang 2.0
> [ ] +0 Huh? Sure, let me sleep.
> [ ] -0 Lang? Sounds bad.
> [ ] -1 I hate you guys.
>
> [http://www.apache.org/~bayard/commons-lang-2.0/ <-- FIXED TYPO
> contains what I am planning to use
> as the build, we will not be using Maven as the site for 2.0, but I
> generate it for reference]
>
> What's not going:
> ----------------
>
> lang.functor has been removed from Lang. Collections will gain what it
> needs and [Functor] will be looked to for the complete functor-style
> solution.
>
> lang.reflect is not ready yet.
>
> lang.util.Identifier is not ready yet.
>
> New maven configuration with the aim of moving Lang to a mavenised site.
>
> What's new:
> ----------
>
> lang.math.* package, which contains Range classes, RandomUtils and a
> Fraction class.
>
> In the top level package, we see a series of additions. There are a set of
> reusable Exceptions which provide slightly tighter meaning than their
> Commons Lang superclasses, IllegalClassException and
> NotImplementedException are examples of these. We also see the addition of
> more Utils classes:
>
> ArrayUtils
> BooleanUtils
> ClassUtils
> StringEscapeUtils
> StringPrintWriter
> WordUtils
>
> We also see the addition of
>
> Validate class [akin to JUnit Assert in style] and BitField from the old
> Commons Util project [as created by POI].
>
> What's changed:
> --------------
>
> ToStringBuilder has gained an inner class.
> builder.* packages have gained new methods
> NumberUtils has a series of constants, LONG_ZERO, LONG_ONE etc.
> StringUtils has a series of new methods.
> The order in which a nested exception is printed has been reversed and a
> static legacy option left to reverse it the other way if desired. This
> now matches JDK 1.4 direction.
>
> What's gone:
> -----------
>
> lang.NumberRange is gone as it has now moved into the math subpackage.
>
> The release:
> -----------
>
> Following a successful vote, the PMC will be notified of the desire to
> release and the instructions at
> http://jakarta.apache.org/commons/releases/ followed to create a
> release. A changelog with 'jardiff' will be included and JDiff will be
> used to generate a site showing changes [as shown in
> http://www.apache.org/~bayard/commons-lang-2.0/Commons-Lang-1.0.1-to-2.0/changes.html].
>
> Hen
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
RE: [VOTE] Release of Commons Lang 2.0 [take 2]
Posted by "Noel J. Bergman" <no...@devtech.com>.
> Well, if there is a question about policy/process, why not just freeze the
> code and restart the vote?
By tagging the CVS, he effectively has frozen the code for the Release. I
was simply curious about the policy because, as I said, other projects are
stricter. For example the HTTPd team has different rules
(http://httpd.apache.org/dev/release.html).
A Release Manager makes a release build, and it is automatically an alpha.
It becomes a beta release when at least three Committers have voted beta
status, and there are more +1 than -1. It becomes a GA release when at
least three Committers vote for GA (stable) status, and there are more +1
than -1. Notice that -1 is not a veto. Notice, also, that the package
itself may go through multiple status changes, but no packaging changes.
The only allowable change is renaming the file to reflect the change in
status; exceptions can be made if a change in the contents of the tarball
(e.g., someone forgot to add the LICENSE file). Otherwise, if a change in
the CVS needs to be incorporated, it becomes a new release (with a new
vote).
Other projects, such as Avalon, also roll jars and then vote on them as a
Release. So I was just asking to understand what is established as policy
here. I wasn't challenging Henri's release.
--- Noel
RE: [VOTE] Release of Commons Lang 2.0 [take 2]
Posted by Phil Steitz <st...@yahoo.com>.
--- "Noel J. Bergman" <no...@devtech.com> wrote:
> > There's a 2_0 tag on the CVS which represents the release material, so
> > continued development shouldn't affect that.
>
> > What I've been doing since the Thursday night tagging was to cvs tag
> the
> > javadoc-fixed files to 2_0 [after checking the change was 'harmless'],
> > but I know this is a bit of a hackish approach. With the couple of cvs
> > commits we've had since the call for a vote, I was planning to add them
> > onto the tag as well.
>
> Based on the nature of them, assuming that your unit tests run, that
> seems
> reasonable. I was just curious about the policy. The httpd group, for
> example, seems to have stricter rules on a Release vote.
>
> --- Noel
>
Well, if there is a question about policy/process, why not just freeze the
code and restart the vote?
Phil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
RE: [VOTE] Release of Commons Lang 2.0 [take 2]
Posted by "Noel J. Bergman" <no...@devtech.com>.
> There's a 2_0 tag on the CVS which represents the release material, so
> continued development shouldn't affect that.
> What I've been doing since the Thursday night tagging was to cvs tag the
> javadoc-fixed files to 2_0 [after checking the change was 'harmless'],
> but I know this is a bit of a hackish approach. With the couple of cvs
> commits we've had since the call for a vote, I was planning to add them
> onto the tag as well.
Based on the nature of them, assuming that your unit tests run, that seems
reasonable. I was just curious about the policy. The httpd group, for
example, seems to have stricter rules on a Release vote.
--- Noel
RE: [VOTE] Release of Commons Lang 2.0 [take 2]
Posted by Henri Yandell <ba...@generationjava.com>.
On Sat, 23 Aug 2003, Noel J. Bergman wrote:
> From: "Henri Yandell" <ba...@generationjava.com>
> > So, without further ado, I'll repeat my call for a VOTE last May.
>
> From what I'm reading, a release makes sense, but what is this group's
> policy regarding making changes during the vote? I know that it is just a
> bit of cleanup (a few wholely appropriate method renames, and improved
> javadocs).
There's a 2_0 tag on the CVS which represents the release material, so
continued development shouldn't affect that.
The last change for 2.0 that wasn't a javadoc change, or related to the
release process was on Thursday night, when a unreleased method was
renamed.
There have been 2.1/3.0 commits in terms of improvement to the Maven
files.
What I've been doing since the Thursday night tagging was to cvs tag the
javadoc-fixed files to 2_0 [after checking the change was 'harmless'], but
I know this is a bit of a hackish approach. With the couple of cvs commits
we've had since the call for a vote, I was planning to add them onto the
tag as well.
With all the slowness on the Apache servers due to the virus [took 3 hours
for the VOTE to actually arrive in my inbox], I've been figuring I'd leave
the VOTE open for a -1 until Monday night EST.
Hen
RE: [VOTE] Release of Commons Lang 2.0 [take 2]
Posted by "Noel J. Bergman" <no...@devtech.com>.
From: "Henri Yandell" <ba...@generationjava.com>
> So, without further ado, I'll repeat my call for a VOTE last May.
Re: [VOTE] Release of Commons Lang 2.0 [take 2]
Posted by Stephen Colebourne <sc...@btopenworld.com>.
+1
----- Original Message -----
From: "Henri Yandell" <ba...@generationjava.com>
> We've already called a vote on this back in May, but a -1 that wanted us
> to include Lang.time caused us to delay and since then we've been dealing
> with more minutae.
>
> So, without further ado, I'll repeat my call for a VOTE last May. The
> information on what has changed below is largely the same as it was in
> May.
>
> The largest change since May not reflected below is a big push on Unit
> Tests [thanks to Clover's superb visualisation, we've got about 88%
> coverage in Clover] and documentation [thanks to Maven and JDiff].
>
> ========================================================================
>
> Our t's are dotted and our i's are crossed, so we'd like to make a
> release of Commons Lang 2.0.
>
> [ ] +1 I support Commons Lang 2.0
> [ ] +0 Huh? Sure, let me sleep.
> [ ] -0 Lang? Sounds bad.
> [ ] -1 I hate you guys.
>
> [http://www.apache.org/~bayard/lang2.0/ contains what I am planning to use
> as the build, we will not be using Maven as the site for 2.0, but I
> generate it for reference]
>
> What's not going:
> ----------------
>
> lang.functor has been removed from Lang. Collections will gain what it
> needs and [Functor] will be looked to for the complete functor-style
> solution.
>
> lang.reflect is not ready yet.
>
> lang.util.Identifier is not ready yet.
>
> New maven configuration with the aim of moving Lang to a mavenised site.
>
> What's new:
> ----------
>
> lang.math.* package, which contains Range classes, RandomUtils and a
> Fraction class.
>
> In the top level package, we see a series of additions. There are a set of
> reusable Exceptions which provide slightly tighter meaning than their
> Commons Lang superclasses, IllegalClassException and
> NotImplementedException are examples of these. We also see the addition of
> more Utils classes:
>
> ArrayUtils
> BooleanUtils
> ClassUtils
> StringEscapeUtils
> StringPrintWriter
> WordUtils
>
> We also see the addition of
>
> Validate class [akin to JUnit Assert in style] and BitField from the old
> Commons Util project [as created by POI].
>
> What's changed:
> --------------
>
> ToStringBuilder has gained an inner class.
> builder.* packages have gained new methods
> NumberUtils has a series of constants, LONG_ZERO, LONG_ONE etc.
> StringUtils has a series of new methods.
> The order in which a nested exception is printed has been reversed and a
> static legacy option left to reverse it the other way if desired. This
> now matches JDK 1.4 direction.
>
> What's gone:
> -----------
>
> lang.NumberRange is gone as it has now moved into the math subpackage.
>
> The release:
> -----------
>
> Following a successful vote, the PMC will be notified of the desire to
> release and the instructions at
> http://jakarta.apache.org/commons/releases/ followed to create a
> release. A changelog with 'jardiff' will be included and JDiff will be
> used to generate a site showing changes [as shown in
>
http://www.apache.org/~bayard/commons-lang-2.0/Commons-Lang-1.0.1-to-2.0/cha
nges.html].
>
> Hen
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
RE: [VOTE] Release of Commons Lang 2.0 [take 2]
Posted by Steven Caswell <st...@mungoknotwise.com>.
+1
Steven Caswell
steve@mungoknotwise.com
a.k.a Mungo Knotwise of Michel Delving
"One ring to rule them all, one ring to find them..."
> -----Original Message-----
> From: Henri Yandell [mailto:bayard@generationjava.com]
> Sent: Friday, August 22, 2003 9:55 AM
> To: Jakarta Commons Developers List
> Cc: Jakarta Project Management Committee List
> Subject: [VOTE] Release of Commons Lang 2.0 [take 2]
>
>
>
> We've already called a vote on this back in May, but a -1
> that wanted us to include Lang.time caused us to delay and
> since then we've been dealing with more minutae.
>
> So, without further ado, I'll repeat my call for a VOTE last
> May. The information on what has changed below is largely the
> same as it was in May.
>
> The largest change since May not reflected below is a big
> push on Unit Tests [thanks to Clover's superb visualisation,
> we've got about 88% coverage in Clover] and documentation
> [thanks to Maven and JDiff].
>
> ==============================================================
> ==========
>
> Our t's are dotted and our i's are crossed, so we'd like to
> make a release of Commons Lang 2.0.
>
> [X] +1 I support Commons Lang 2.0
> [ ] +0 Huh? Sure, let me sleep.
> [ ] -0 Lang? Sounds bad.
> [ ] -1 I hate you guys.
>
> [http://www.apache.org/~bayard/lang2.0/ contains what I am
> planning to use as the build, we will not be using Maven as
> the site for 2.0, but I generate it for reference]
>
> What's not going:
> ----------------
>
> lang.functor has been removed from Lang. Collections will
> gain what it needs and [Functor] will be looked to for the
> complete functor-style solution.
>
> lang.reflect is not ready yet.
>
> lang.util.Identifier is not ready yet.
>
> New maven configuration with the aim of moving Lang to a
> mavenised site.
>
> What's new:
> ----------
>
> lang.math.* package, which contains Range classes,
> RandomUtils and a Fraction class.
>
> In the top level package, we see a series of additions. There
> are a set of reusable Exceptions which provide slightly
> tighter meaning than their Commons Lang superclasses,
> IllegalClassException and NotImplementedException are
> examples of these. We also see the addition of more Utils classes:
>
> ArrayUtils
> BooleanUtils
> ClassUtils
> StringEscapeUtils
> StringPrintWriter
> WordUtils
>
> We also see the addition of
>
> Validate class [akin to JUnit Assert in style] and BitField
> from the old Commons Util project [as created by POI].
>
> What's changed:
> --------------
>
> ToStringBuilder has gained an inner class.
> builder.* packages have gained new methods
> NumberUtils has a series of constants, LONG_ZERO, LONG_ONE
> etc. StringUtils has a series of new methods. The order in
> which a nested exception is printed has been reversed and a
> static legacy option left to reverse it the other way if
> desired. This now matches JDK 1.4 direction.
>
> What's gone:
> -----------
>
> lang.NumberRange is gone as it has now moved into the math subpackage.
>
> The release:
> -----------
>
> Following a successful vote, the PMC will be notified of the
> desire to release and the instructions at
> http://jakarta.apache.org/commons/releases/ > followed to
> create a release. A changelog with 'jardiff' will be included
> and JDiff will be used to generate a site showing changes [as
> shown in
> http://www.apache.org/~bayard/commons-lang-2.0/Commons-Lang-1.
0.1-to-2.0/changes.html].
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org