You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Niall Pemberton <ni...@gmail.com> on 2010/02/03 03:22:05 UTC
[lang] Preparing for a 2.5 release
For anyone who hasn't noticed I've been back-porting Commons Lang
changes from the trunk to a 2.x branch:
http://svn.apache.org/viewvc/commons/proper/lang/branches/LANG_2_X/
AFAIC its getting close to being ready for a 2.5 release. LANG-204 is
currently in progress and I will try to post a summary of whats been
back ported (and what hasn't) tomorrow. Other than that I have only
updating the site and getting the release notes & changes plugin up to
date on my todo list.
Is there anything anyone else wants included?
Niall
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] Preparing for a 2.5 release
Posted by Matt Benson <gu...@gmail.com>.
I'll only say that not autoboxing by default is already over-paranoid
when you consider that you're usually talking about doing reflective
invocations, for which Objects (and therefore unboxing) are needed to
make calls with primitive arguments. If you're talking about
compiler-level stuff, the RT check seems more in line. But I don't
feel strongly enough about it to debate the issue.
br,
Matt
On Feb 3, 2010, at 9:47 AM, Niall Pemberton wrote:
> On Wed, Feb 3, 2010 at 3:28 PM, Matt Benson <gu...@gmail.com>
> wrote:
>> If you're offering, the changes I made yesterday to ClassUtils to
>> default
>> autoboxing based on RT Java version should probably be ported.
>> After that,
>> autoboxing can actually just be defaulted to true in trunk as it will
>> require Java 5+ at RT.
>
> I did look at that, but its a change in how its currently working
> which is possibly a compatibility issue. Perhaps thats being over
> paranoid though.
>
> Niall
>
>> Thanks,
>> Matt
>>
>> On Feb 2, 2010, at 8:22 PM, Niall Pemberton wrote:
>>
>>> For anyone who hasn't noticed I've been back-porting Commons Lang
>>> changes from the trunk to a 2.x branch:
>>>
>>> http://svn.apache.org/viewvc/commons/proper/lang/branches/
>>> LANG_2_X/
>>>
>>> AFAIC its getting close to being ready for a 2.5 release.
>>> LANG-204 is
>>> currently in progress and I will try to post a summary of whats been
>>> back ported (and what hasn't) tomorrow. Other than that I have only
>>> updating the site and getting the release notes & changes plugin
>>> up to
>>> date on my todo list.
>>>
>>> Is there anything anyone else wants included?
>>>
>>> Niall
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] Preparing for a 2.5 release
Posted by Niall Pemberton <ni...@gmail.com>.
On Wed, Feb 3, 2010 at 3:28 PM, Matt Benson <gu...@gmail.com> wrote:
> If you're offering, the changes I made yesterday to ClassUtils to default
> autoboxing based on RT Java version should probably be ported. After that,
> autoboxing can actually just be defaulted to true in trunk as it will
> require Java 5+ at RT.
I did look at that, but its a change in how its currently working
which is possibly a compatibility issue. Perhaps thats being over
paranoid though.
Niall
> Thanks,
> Matt
>
> On Feb 2, 2010, at 8:22 PM, Niall Pemberton wrote:
>
>> For anyone who hasn't noticed I've been back-porting Commons Lang
>> changes from the trunk to a 2.x branch:
>>
>> http://svn.apache.org/viewvc/commons/proper/lang/branches/LANG_2_X/
>>
>> AFAIC its getting close to being ready for a 2.5 release. LANG-204 is
>> currently in progress and I will try to post a summary of whats been
>> back ported (and what hasn't) tomorrow. Other than that I have only
>> updating the site and getting the release notes & changes plugin up to
>> date on my todo list.
>>
>> Is there anything anyone else wants included?
>>
>> Niall
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] Preparing for a 2.5 release
Posted by Matt Benson <gu...@gmail.com>.
If you're offering, the changes I made yesterday to ClassUtils to
default autoboxing based on RT Java version should probably be
ported. After that, autoboxing can actually just be defaulted to
true in trunk as it will require Java 5+ at RT.
Thanks,
Matt
On Feb 2, 2010, at 8:22 PM, Niall Pemberton wrote:
> For anyone who hasn't noticed I've been back-porting Commons Lang
> changes from the trunk to a 2.x branch:
>
> http://svn.apache.org/viewvc/commons/proper/lang/branches/
> LANG_2_X/
>
> AFAIC its getting close to being ready for a 2.5 release. LANG-204 is
> currently in progress and I will try to post a summary of whats been
> back ported (and what hasn't) tomorrow. Other than that I have only
> updating the site and getting the release notes & changes plugin up to
> date on my todo list.
>
> Is there anything anyone else wants included?
>
> Niall
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] Preparing for a 2.5 release
Posted by sebb <se...@gmail.com>.
On 03/02/2010, Niall Pemberton <ni...@gmail.com> wrote:
> On Wed, Feb 3, 2010 at 2:22 AM, Niall Pemberton
> <ni...@gmail.com> wrote:
> > For anyone who hasn't noticed I've been back-porting Commons Lang
> > changes from the trunk to a 2.x branch:
> >
> > http://svn.apache.org/viewvc/commons/proper/lang/branches/LANG_2_X/
> >
> > AFAIC its getting close to being ready for a 2.5 release. LANG-204 is
> > currently in progress and I will try to post a summary of whats been
> > back ported (and what hasn't) tomorrow. Other than that I have only
> > updating the site and getting the release notes & changes plugin up to
> > date on my todo list.
> >
> > Is there anything anyone else wants included?
>
>
> Currently the other Lang bugs against 2.x are the following, but I
> don't plan to fix them unless someone else supplies a patch:
>
> http://issues.apache.org/jira/browse/LANG-76
I hope to take a look at this later - LANG-153 has a test case which
should help.
> http://issues.apache.org/jira/browse/LANG-331
> http://issues.apache.org/jira/browse/LANG-472
Might look at that too.
>
If any of the bugs are not fixed, I think it would be worth adding
details to the Javadoc of the affected classes, or at least mentioning
them in the release notes.
>
> > Niall
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] Preparing for a 2.5 release
Posted by Niall Pemberton <ni...@gmail.com>.
On Wed, Feb 3, 2010 at 2:22 AM, Niall Pemberton
<ni...@gmail.com> wrote:
> For anyone who hasn't noticed I've been back-porting Commons Lang
> changes from the trunk to a 2.x branch:
>
> http://svn.apache.org/viewvc/commons/proper/lang/branches/LANG_2_X/
>
> AFAIC its getting close to being ready for a 2.5 release. LANG-204 is
> currently in progress and I will try to post a summary of whats been
> back ported (and what hasn't) tomorrow. Other than that I have only
> updating the site and getting the release notes & changes plugin up to
> date on my todo list.
>
> Is there anything anyone else wants included?
Currently the other Lang bugs against 2.x are the following, but I
don't plan to fix them unless someone else supplies a patch:
http://issues.apache.org/jira/browse/LANG-76
http://issues.apache.org/jira/browse/LANG-331
http://issues.apache.org/jira/browse/LANG-472
> Niall
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] Preparing for a 2.5 release
Posted by Niall Pemberton <ni...@gmail.com>.
On Sun, Feb 7, 2010 at 3:07 AM, Henri Yandell <fl...@gmail.com> wrote:
> On Sat, Feb 6, 2010 at 12:40 PM, Niall Pemberton
> <ni...@gmail.com> wrote:
>> On Fri, Feb 5, 2010 at 4:20 AM, Henri Yandell <fl...@gmail.com> wrote:
>>> My general thinking is:
>>>
>>> "+1, thanks for doing this"
>>>
>>> mixed with:
>>>
>>> "We now have two versions in development at the same time, we can no
>>> longer just charge along coding - we need process"
>>>
>>> Namely, do we put anything in 2.5 as long as it doesn't affect
>>> backwards compat, do we keep adding enhancements, do we only do
>>> bugfixes (or critical bugfixes)?
>>
>> ATM its just backporting compatible trunk changes. So were not adding
>> things to the branch that aren't in the trunk. IMO what gets
>> backported should be down to those willing to do the work. Why would
>> you want to dictate what someone can or can't do?
>
> Trying to avoid two divergent products and the user confusion. It's
> 2.5 instead of 2.4.1, we're adding new features from 3.0 rather than
> just focusing on bugfixes so now we have two Commons Langs.
>
> Should I be making a JDK 1.3 version of Range.java?
>
> Should we add 'JDK 6' features implemented for JDK 1.3?
>
> Basically trying to make sure we don't end up with CLI1 and CLI2 :)
If someone wants to do something different in the 2.x branch from
trunk, then I think it needs to be discussed first. But if its just
backporting features from trunk then we don't have this issue.
>>> It starts to feel that we need to emulate Tomcat's methodology more of
>>> working in trunk then voting particular patches back into the legacy
>>> version.
>>
>> I'm -1 to this. Tomcat's methodology arose out of the acrimony within
>> their PMC. That situation doesn't exist here so I don't see why we
>> would want to make this unnecessarily beaurocratic.
>
> Regardless of origin, I've liked watching it from a bugfix branch
> point of view.
Watching is one thing. Having to operate an additional beaurocratic
process needs good reason IMO. I doubt the Tomcat people really wanted
to operate that way - but it was better than the acrimony that
preceeded it.
Niall
> Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] Preparing for a 2.5 release
Posted by Henri Yandell <fl...@gmail.com>.
On Sat, Feb 6, 2010 at 12:40 PM, Niall Pemberton
<ni...@gmail.com> wrote:
> On Fri, Feb 5, 2010 at 4:20 AM, Henri Yandell <fl...@gmail.com> wrote:
>> My general thinking is:
>>
>> "+1, thanks for doing this"
>>
>> mixed with:
>>
>> "We now have two versions in development at the same time, we can no
>> longer just charge along coding - we need process"
>>
>> Namely, do we put anything in 2.5 as long as it doesn't affect
>> backwards compat, do we keep adding enhancements, do we only do
>> bugfixes (or critical bugfixes)?
>
> ATM its just backporting compatible trunk changes. So were not adding
> things to the branch that aren't in the trunk. IMO what gets
> backported should be down to those willing to do the work. Why would
> you want to dictate what someone can or can't do?
Trying to avoid two divergent products and the user confusion. It's
2.5 instead of 2.4.1, we're adding new features from 3.0 rather than
just focusing on bugfixes so now we have two Commons Langs.
Should I be making a JDK 1.3 version of Range.java?
Should we add 'JDK 6' features implemented for JDK 1.3?
Basically trying to make sure we don't end up with CLI1 and CLI2 :)
>> It starts to feel that we need to emulate Tomcat's methodology more of
>> working in trunk then voting particular patches back into the legacy
>> version.
>
> I'm -1 to this. Tomcat's methodology arose out of the acrimony within
> their PMC. That situation doesn't exist here so I don't see why we
> would want to make this unnecessarily beaurocratic.
Regardless of origin, I've liked watching it from a bugfix branch
point of view.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] Preparing for a 2.5 release
Posted by Niall Pemberton <ni...@gmail.com>.
On Fri, Feb 5, 2010 at 4:20 AM, Henri Yandell <fl...@gmail.com> wrote:
> My general thinking is:
>
> "+1, thanks for doing this"
>
> mixed with:
>
> "We now have two versions in development at the same time, we can no
> longer just charge along coding - we need process"
>
> Namely, do we put anything in 2.5 as long as it doesn't affect
> backwards compat, do we keep adding enhancements, do we only do
> bugfixes (or critical bugfixes)?
ATM its just backporting compatible trunk changes. So were not adding
things to the branch that aren't in the trunk. IMO what gets
backported should be down to those willing to do the work. Why would
you want to dictate what someone can or can't do?
> It starts to feel that we need to emulate Tomcat's methodology more of
> working in trunk then voting particular patches back into the legacy
> version.
I'm -1 to this. Tomcat's methodology arose out of the acrimony within
their PMC. That situation doesn't exist here so I don't see why we
would want to make this unnecessarily beaurocratic.
Niall
> Hen
>
> On Tue, Feb 2, 2010 at 6:22 PM, Niall Pemberton
> <ni...@gmail.com> wrote:
>> For anyone who hasn't noticed I've been back-porting Commons Lang
>> changes from the trunk to a 2.x branch:
>>
>> http://svn.apache.org/viewvc/commons/proper/lang/branches/LANG_2_X/
>>
>> AFAIC its getting close to being ready for a 2.5 release. LANG-204 is
>> currently in progress and I will try to post a summary of whats been
>> back ported (and what hasn't) tomorrow. Other than that I have only
>> updating the site and getting the release notes & changes plugin up to
>> date on my todo list.
>>
>> Is there anything anyone else wants included?
>>
>> Niall
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] Preparing for a 2.5 release
Posted by Henri Yandell <fl...@gmail.com>.
My general thinking is:
"+1, thanks for doing this"
mixed with:
"We now have two versions in development at the same time, we can no
longer just charge along coding - we need process"
Namely, do we put anything in 2.5 as long as it doesn't affect
backwards compat, do we keep adding enhancements, do we only do
bugfixes (or critical bugfixes)?
It starts to feel that we need to emulate Tomcat's methodology more of
working in trunk then voting particular patches back into the legacy
version.
Hen
On Tue, Feb 2, 2010 at 6:22 PM, Niall Pemberton
<ni...@gmail.com> wrote:
> For anyone who hasn't noticed I've been back-porting Commons Lang
> changes from the trunk to a 2.x branch:
>
> http://svn.apache.org/viewvc/commons/proper/lang/branches/LANG_2_X/
>
> AFAIC its getting close to being ready for a 2.5 release. LANG-204 is
> currently in progress and I will try to post a summary of whats been
> back ported (and what hasn't) tomorrow. Other than that I have only
> updating the site and getting the release notes & changes plugin up to
> date on my todo list.
>
> Is there anything anyone else wants included?
>
> Niall
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org