You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Matt Benson <gu...@gmail.com> on 2011/06/18 01:53:36 UTC
Re: [lang] Time for RC3?
Hen,
Despite my pathological fear of the RM role, especially in
conjunction with Maven, I am contemplating picking this up since my
kids are so much older than yours. Do you have any objection to my
removing your RC3 svn tag?
br,
Matt
On Fri, Apr 29, 2011 at 12:56 AM, Henri Yandell <fl...@gmail.com> wrote:
> On Wed, Apr 27, 2011 at 9:58 PM, Henri Yandell <fl...@gmail.com> wrote:
>> On Fri, Apr 22, 2011 at 11:36 PM, Henri Yandell <fl...@gmail.com> wrote:
>>> These are the current blocking items in play afaik:
>>>
>>> * Email thread - what else should implement Formattable?
>>
>> Sounds like this is now:
>>
>> * Update javadoc for Mutable classes to indicate that they can't do
>> much to make them useful in String.format.
>>
>> We could consider making Fraction, StopWatch and others use Format
>> under the hood and thus implementing Formattable, but I'm not sure I
>> see much point. I also don't see adding Formattable later on as a
>> backwards compat issue, but maybe I'm being dim (flu + newborn,
>> verrrrry dim right now).
>
> Note, I don't consider either of these to be required for 3.0. I've
> documented the javadoc as LANG-698 and the consideration of adding
> Formattable as LANG-699.
>
>>> * LANG-696/Email thread - getShortName. What to do with the (String)
>>> variant. Remove others.
>>
>> I've updated LANG-696. I think we need to decide which of the following we want:
>>
>> getSimpleName(Map.Entry.class) => "Entry" [Matches JVM]
>> getSimpleName(Map.Entry.class) => "Map.Entry" [Matches Lang 2.x]
>
> I think we should think more on this (i.e. post 3.0) and it's not the
> end of the world to be stuck with getSimpleName until 4.0.
>
> Hen
>
> ---------------------------------------------------------------------
> 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] Time for RC3?
Posted by Henri Yandell <fl...@gmail.com>.
Assuming no one vetos my r1090111 rollback, I think we can go for an
RC4. There are non-API bugs in JIRA, but I'd rather we release with
some bugs and then start fixing/releasing than continually get held
up.
How are you timewise for RC4 Matt? I'm still very kidbound, but
beginning to get some time back.
Hen
On Fri, Jun 17, 2011 at 10:39 PM, Henri Yandell <fl...@gmail.com> wrote:
> On Fri, Jun 17, 2011 at 8:17 PM, Matt Benson <gu...@gmail.com> wrote:
>> On Fri, Jun 17, 2011 at 9:00 PM, Henri Yandell <fl...@gmail.com> wrote:
>>> We had an RC3 vote so shouldn't remove; but I'm very happy if you've
>>> time to do an RC4. I've been managing about enough time to look at the
>>> outstanding issues before I'm back to the diapers.
>>>
>>
>> That's why I asked... I couldn't find the evidence of the RC3 vote for
>> some reason, but I'll take your word for it.
>
> I injected a little confusion by having two threads :)
>
> http://commons.markmail.org/thread/dxmser7yfew37sqb
> http://commons.markmail.org/thread/xk34bmkoz6jctt7g
>
>>> Which is 'what's in JIRA' plus the discussion on the text.translate/Range API.
>>
>> JIRA seems clear, no? Do we need to wait on the other issue, then?
>
> The thread was:
>
> "[LANG] unnecessary boxing in StringEscapeUtils etc"
>
> Sebb had a complaint re: performance concerns with boxing and Stephen
> suggested a solution, while also considering the performance issue
> minor.
>
> I spent some time a week back playing with the API as I disliked the
> overlap between Range<Integer> and Range<Character>. Autoboxing,
> generics and char-int conversion all get fiddly in the API and not
> nice.
>
> I'm tempted to move the current (Range<Integer>) constructors to a
> static factory method, and then go ahead and release - text.translate
> is not a major part of the Lang API. The reason for doing that is so
> that we can deprecate it later on if desired and not have to worry
> about lots of clashing with the replacement methods.
>
> Hen
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] Time for RC3?
Posted by Henri Yandell <fl...@gmail.com>.
On Fri, Jun 17, 2011 at 8:17 PM, Matt Benson <gu...@gmail.com> wrote:
> On Fri, Jun 17, 2011 at 9:00 PM, Henri Yandell <fl...@gmail.com> wrote:
>> We had an RC3 vote so shouldn't remove; but I'm very happy if you've
>> time to do an RC4. I've been managing about enough time to look at the
>> outstanding issues before I'm back to the diapers.
>>
>
> That's why I asked... I couldn't find the evidence of the RC3 vote for
> some reason, but I'll take your word for it.
I injected a little confusion by having two threads :)
http://commons.markmail.org/thread/dxmser7yfew37sqb
http://commons.markmail.org/thread/xk34bmkoz6jctt7g
>> Which is 'what's in JIRA' plus the discussion on the text.translate/Range API.
>
> JIRA seems clear, no? Do we need to wait on the other issue, then?
The thread was:
"[LANG] unnecessary boxing in StringEscapeUtils etc"
Sebb had a complaint re: performance concerns with boxing and Stephen
suggested a solution, while also considering the performance issue
minor.
I spent some time a week back playing with the API as I disliked the
overlap between Range<Integer> and Range<Character>. Autoboxing,
generics and char-int conversion all get fiddly in the API and not
nice.
I'm tempted to move the current (Range<Integer>) constructors to a
static factory method, and then go ahead and release - text.translate
is not a major part of the Lang API. The reason for doing that is so
that we can deprecate it later on if desired and not have to worry
about lots of clashing with the replacement methods.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] Time for RC3?
Posted by Matt Benson <gu...@gmail.com>.
On Fri, Jun 17, 2011 at 9:00 PM, Henri Yandell <fl...@gmail.com> wrote:
> We had an RC3 vote so shouldn't remove; but I'm very happy if you've
> time to do an RC4. I've been managing about enough time to look at the
> outstanding issues before I'm back to the diapers.
>
That's why I asked... I couldn't find the evidence of the RC3 vote for
some reason, but I'll take your word for it.
> Which is 'what's in JIRA' plus the discussion on the text.translate/Range API.
JIRA seems clear, no? Do we need to wait on the other issue, then?
Matt
>
> Hen
>
> On Fri, Jun 17, 2011 at 4:53 PM, Matt Benson <gu...@gmail.com> wrote:
>> Hen,
>> Despite my pathological fear of the RM role, especially in
>> conjunction with Maven, I am contemplating picking this up since my
>> kids are so much older than yours. Do you have any objection to my
>> removing your RC3 svn tag?
>>
>> br,
>> Matt
>>
>> On Fri, Apr 29, 2011 at 12:56 AM, Henri Yandell <fl...@gmail.com> wrote:
>>> On Wed, Apr 27, 2011 at 9:58 PM, Henri Yandell <fl...@gmail.com> wrote:
>>>> On Fri, Apr 22, 2011 at 11:36 PM, Henri Yandell <fl...@gmail.com> wrote:
>>>>> These are the current blocking items in play afaik:
>>>>>
>>>>> * Email thread - what else should implement Formattable?
>>>>
>>>> Sounds like this is now:
>>>>
>>>> * Update javadoc for Mutable classes to indicate that they can't do
>>>> much to make them useful in String.format.
>>>>
>>>> We could consider making Fraction, StopWatch and others use Format
>>>> under the hood and thus implementing Formattable, but I'm not sure I
>>>> see much point. I also don't see adding Formattable later on as a
>>>> backwards compat issue, but maybe I'm being dim (flu + newborn,
>>>> verrrrry dim right now).
>>>
>>> Note, I don't consider either of these to be required for 3.0. I've
>>> documented the javadoc as LANG-698 and the consideration of adding
>>> Formattable as LANG-699.
>>>
>>>>> * LANG-696/Email thread - getShortName. What to do with the (String)
>>>>> variant. Remove others.
>>>>
>>>> I've updated LANG-696. I think we need to decide which of the following we want:
>>>>
>>>> getSimpleName(Map.Entry.class) => "Entry" [Matches JVM]
>>>> getSimpleName(Map.Entry.class) => "Map.Entry" [Matches Lang 2.x]
>>>
>>> I think we should think more on this (i.e. post 3.0) and it's not the
>>> end of the world to be stuck with getSimpleName until 4.0.
>>>
>>> Hen
>>>
>>> ---------------------------------------------------------------------
>>> 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] Time for RC3?
Posted by Henri Yandell <fl...@gmail.com>.
We had an RC3 vote so shouldn't remove; but I'm very happy if you've
time to do an RC4. I've been managing about enough time to look at the
outstanding issues before I'm back to the diapers.
Which is 'what's in JIRA' plus the discussion on the text.translate/Range API.
Hen
On Fri, Jun 17, 2011 at 4:53 PM, Matt Benson <gu...@gmail.com> wrote:
> Hen,
> Despite my pathological fear of the RM role, especially in
> conjunction with Maven, I am contemplating picking this up since my
> kids are so much older than yours. Do you have any objection to my
> removing your RC3 svn tag?
>
> br,
> Matt
>
> On Fri, Apr 29, 2011 at 12:56 AM, Henri Yandell <fl...@gmail.com> wrote:
>> On Wed, Apr 27, 2011 at 9:58 PM, Henri Yandell <fl...@gmail.com> wrote:
>>> On Fri, Apr 22, 2011 at 11:36 PM, Henri Yandell <fl...@gmail.com> wrote:
>>>> These are the current blocking items in play afaik:
>>>>
>>>> * Email thread - what else should implement Formattable?
>>>
>>> Sounds like this is now:
>>>
>>> * Update javadoc for Mutable classes to indicate that they can't do
>>> much to make them useful in String.format.
>>>
>>> We could consider making Fraction, StopWatch and others use Format
>>> under the hood and thus implementing Formattable, but I'm not sure I
>>> see much point. I also don't see adding Formattable later on as a
>>> backwards compat issue, but maybe I'm being dim (flu + newborn,
>>> verrrrry dim right now).
>>
>> Note, I don't consider either of these to be required for 3.0. I've
>> documented the javadoc as LANG-698 and the consideration of adding
>> Formattable as LANG-699.
>>
>>>> * LANG-696/Email thread - getShortName. What to do with the (String)
>>>> variant. Remove others.
>>>
>>> I've updated LANG-696. I think we need to decide which of the following we want:
>>>
>>> getSimpleName(Map.Entry.class) => "Entry" [Matches JVM]
>>> getSimpleName(Map.Entry.class) => "Map.Entry" [Matches Lang 2.x]
>>
>> I think we should think more on this (i.e. post 3.0) and it's not the
>> end of the world to be stuck with getSimpleName until 4.0.
>>
>> Hen
>>
>> ---------------------------------------------------------------------
>> 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