+1
Gary
Original message
From: Duncan Jones
Date:02/07/2014 05:48 (GMT-05:00)
To: Commons Developers List
Subject: Re: [LANG] Towards 3.3
On 31 January 2014 07:54, Benedikt Ritter wrote:
> Nice discussion. Thanks for clearing this up. So Duncan: go ahead if you
&g
2014-02-07 Duncan Jones :
> On 31 January 2014 07:54, Benedikt Ritter wrote:
> > Nice discussion. Thanks for clearing this up. So Duncan: go ahead if you
> > got the time.
>
> Hi Benedikt,
>
> Based on other discussions on the ML, the fix for LANG-341 belongs in
> the Conversion class. I think th
On 31 January 2014 07:54, Benedikt Ritter wrote:
> Nice discussion. Thanks for clearing this up. So Duncan: go ahead if you
> got the time.
Hi Benedikt,
Based on other discussions on the ML, the fix for LANG-341 belongs in
the Conversion class. I think this warrants a larger piece of work to
imp
Nice discussion. Thanks for clearing this up. So Duncan: go ahead if you
got the time.
2014/1/31 Duncan Jones
> On 31 January 2014 04:37, Henri Yandell wrote:
> > Read section 5 of the license.
>
> Ok, that's pretty clear-cut then. To save others from dragging up the
> wording:
>
> "5. Submiss
On 31 January 2014 04:37, Henri Yandell wrote:
> Read section 5 of the license.
Ok, that's pretty clear-cut then. To save others from dragging up the wording:
"5. Submission of Contributions. Unless You explicitly state
otherwise, any Contribution intentionally submitted for inclusion in
the Wor
Read section 5 of the license.
On Jan 30, 2014 10:16 AM, "Benedikt Ritter" wrote:
> I'm not sure whether providing a patch for an AL licensed file is
> automatically licensed under AL as well. In the end the raw diff file does
> not contain the AL header, so you're better of with an ICLA.
>
> Be
I'm not sure whether providing a patch for an AL licensed file is
automatically licensed under AL as well. In the end the raw diff file does
not contain the AL header, so you're better of with an ICLA.
Benedikt
2014/1/27 Henri Yandell
> Depends whose arguing probably :)
>
> Our license gives u
Depends whose arguing probably :)
Our license gives us a right to contributions under Apache 2.0 unless
stated otherwise; the ICLA is playing safer. We can also simply take
anything under a compatible license and include (with suitable licensing).
I did that for a method from Spring.
Hen
On Sun
On 26 January 2014 19:47, Duncan Jones wrote:
> On 26 January 2014 18:49, Benedikt Ritter wrote:
>> Hi Duncan,
>>
>>
>> 2014/1/26 Duncan Jones
>>
>>> On 26 January 2014 13:33, Benedikt Ritter wrote:
>>> > Hi all,
>>> >
>>> > we've fixed some bugs and we have some nice new features implemented
>
Adding more features and fixes is Ok but at this point I'd rather regular early
and release often.
G
Original message
From: Duncan Jones
Date:01/26/2014 11:45 (GMT-05:00)
To: Commons Developers List
Subject: Re: [LANG] Towards 3.3
On 26 January 2014 13:33, Ben
On 26 January 2014 18:49, Benedikt Ritter wrote:
> Hi Duncan,
>
>
> 2014/1/26 Duncan Jones
>
>> On 26 January 2014 13:33, Benedikt Ritter wrote:
>> > Hi all,
>> >
>> > we've fixed some bugs and we have some nice new features implemented
>> > (DiffBuilder, Jaro-Winkler Distance, RandomUtils, Clas
Hi Duncan,
2014/1/26 Duncan Jones
> On 26 January 2014 13:33, Benedikt Ritter wrote:
> > Hi all,
> >
> > we've fixed some bugs and we have some nice new features implemented
> > (DiffBuilder, Jaro-Winkler Distance, RandomUtils, ClassPathUtils), so I'm
> > planning to cut a RC in the first week
On 26 January 2014 13:33, Benedikt Ritter wrote:
> Hi all,
>
> we've fixed some bugs and we have some nice new features implemented
> (DiffBuilder, Jaro-Winkler Distance, RandomUtils, ClassPathUtils), so I'm
> planning to cut a RC in the first week of February.
>
> I just wanted to know if there i
Hi all,
we've fixed some bugs and we have some nice new features implemented
(DiffBuilder, Jaro-Winkler Distance, RandomUtils, ClassPathUtils), so I'm
planning to cut a RC in the first week of February.
I just wanted to know if there is anything you'd like to have included in
the next release. Th
14 matches
Mail list logo