You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by Lewis John Mcgibbney <le...@gmail.com> on 2012/11/22 16:15:22 UTC
[DISCUSS] trunk release?
Hi All,
A while ago I asked if it was time to get another release of trunk...
Markus expressed the valid opinion that there were some issues with
recently committed material that had maybe not been given the chance
to mature enough and that could do with more testing.
So far in trunk (since 1.5.1), we've resolved some 45 issues [0], but
we have some critical issues open [1] which could do with some
attention as well.
None of these issues are mine therefore I don't know how those of us
feel (with patches available) about integrating these issues
prior/post 1.6 release... or indeed whether a 1.6 release is welcomed
at the moment? The codebase seems to be stable and getting better so
from my perspective I would back a 1.X release.
All the best for now
Lewis
[0] http://tinyurl.com/cf3vcpr
[1] http://tinyurl.com/d4omnrc
--
Lewis
Re: [DISCUSS] trunk release?
Posted by Lewis John Mcgibbney <le...@gmail.com>.
I'll run the RC this afternoon
On Fri, Nov 23, 2012 at 1:30 AM, Lewis John Mcgibbney
<le...@gmail.com> wrote:
> OK I will pop an RC today
>
> Thank you for the input
>
> Lewis
>
> On Thu, Nov 22, 2012 at 8:43 PM, Sebastian Nagel
> <wa...@googlemail.com> wrote:
>> +1 to release
>>
>> Now we can hold the 6-month cycle.
>> Chris is right: If we manage to address a couple
>> of the critical issues early next year, we can release earlier.
>>
>> Sebastian
>>
>> On 11/22/2012 06:43 PM, Mattmann, Chris A (388J) wrote:
>>> "Release early, release often" :)
>>>
>>> I'd say I'd be happy to try and spin it, but you'd beat me to it so I just
>>> will say I'll be happy to test the RC and voice my VOTE when you roll
>>> it Lewis :)
>>>
>>> Happy Thanksgiving (even though you're not in the States yet)!
>>>
>>> Cheers,
>>> Chris
>>>
>>> On Nov 22, 2012, at 7:15 AM, Lewis John Mcgibbney wrote:
>>>
>>>> Hi All,
>>>>
>>>> A while ago I asked if it was time to get another release of trunk...
>>>> Markus expressed the valid opinion that there were some issues with
>>>> recently committed material that had maybe not been given the chance
>>>> to mature enough and that could do with more testing.
>>>>
>>>> So far in trunk (since 1.5.1), we've resolved some 45 issues [0], but
>>>> we have some critical issues open [1] which could do with some
>>>> attention as well.
>>>> None of these issues are mine therefore I don't know how those of us
>>>> feel (with patches available) about integrating these issues
>>>> prior/post 1.6 release... or indeed whether a 1.6 release is welcomed
>>>> at the moment? The codebase seems to be stable and getting better so
>>>> from my perspective I would back a 1.X release.
>>>>
>>>> All the best for now
>>>>
>>>> Lewis
>>>>
>>>> [0] http://tinyurl.com/cf3vcpr
>>>> [1] http://tinyurl.com/d4omnrc
>>>>
>>>> --
>>>> Lewis
>>>
>>
>
>
>
> --
> Lewis
--
Lewis
Re: [DISCUSS] trunk release?
Posted by Lewis John Mcgibbney <le...@gmail.com>.
OK I will pop an RC today
Thank you for the input
Lewis
On Thu, Nov 22, 2012 at 8:43 PM, Sebastian Nagel
<wa...@googlemail.com> wrote:
> +1 to release
>
> Now we can hold the 6-month cycle.
> Chris is right: If we manage to address a couple
> of the critical issues early next year, we can release earlier.
>
> Sebastian
>
> On 11/22/2012 06:43 PM, Mattmann, Chris A (388J) wrote:
>> "Release early, release often" :)
>>
>> I'd say I'd be happy to try and spin it, but you'd beat me to it so I just
>> will say I'll be happy to test the RC and voice my VOTE when you roll
>> it Lewis :)
>>
>> Happy Thanksgiving (even though you're not in the States yet)!
>>
>> Cheers,
>> Chris
>>
>> On Nov 22, 2012, at 7:15 AM, Lewis John Mcgibbney wrote:
>>
>>> Hi All,
>>>
>>> A while ago I asked if it was time to get another release of trunk...
>>> Markus expressed the valid opinion that there were some issues with
>>> recently committed material that had maybe not been given the chance
>>> to mature enough and that could do with more testing.
>>>
>>> So far in trunk (since 1.5.1), we've resolved some 45 issues [0], but
>>> we have some critical issues open [1] which could do with some
>>> attention as well.
>>> None of these issues are mine therefore I don't know how those of us
>>> feel (with patches available) about integrating these issues
>>> prior/post 1.6 release... or indeed whether a 1.6 release is welcomed
>>> at the moment? The codebase seems to be stable and getting better so
>>> from my perspective I would back a 1.X release.
>>>
>>> All the best for now
>>>
>>> Lewis
>>>
>>> [0] http://tinyurl.com/cf3vcpr
>>> [1] http://tinyurl.com/d4omnrc
>>>
>>> --
>>> Lewis
>>
>
--
Lewis
Re: [DISCUSS] trunk release?
Posted by Sebastian Nagel <wa...@googlemail.com>.
+1 to release
Now we can hold the 6-month cycle.
Chris is right: If we manage to address a couple
of the critical issues early next year, we can release earlier.
Sebastian
On 11/22/2012 06:43 PM, Mattmann, Chris A (388J) wrote:
> "Release early, release often" :)
>
> I'd say I'd be happy to try and spin it, but you'd beat me to it so I just
> will say I'll be happy to test the RC and voice my VOTE when you roll
> it Lewis :)
>
> Happy Thanksgiving (even though you're not in the States yet)!
>
> Cheers,
> Chris
>
> On Nov 22, 2012, at 7:15 AM, Lewis John Mcgibbney wrote:
>
>> Hi All,
>>
>> A while ago I asked if it was time to get another release of trunk...
>> Markus expressed the valid opinion that there were some issues with
>> recently committed material that had maybe not been given the chance
>> to mature enough and that could do with more testing.
>>
>> So far in trunk (since 1.5.1), we've resolved some 45 issues [0], but
>> we have some critical issues open [1] which could do with some
>> attention as well.
>> None of these issues are mine therefore I don't know how those of us
>> feel (with patches available) about integrating these issues
>> prior/post 1.6 release... or indeed whether a 1.6 release is welcomed
>> at the moment? The codebase seems to be stable and getting better so
>> from my perspective I would back a 1.X release.
>>
>> All the best for now
>>
>> Lewis
>>
>> [0] http://tinyurl.com/cf3vcpr
>> [1] http://tinyurl.com/d4omnrc
>>
>> --
>> Lewis
>
RE: [DISCUSS] trunk release?
Posted by Markus Jelsma <ma...@openindex.io>.
-----Original message-----
> From:Lewis John Mcgibbney <le...@gmail.com>
> Sent: Thu 22-Nov-2012 19:23
> To: dev@nutch.apache.org
> Subject: Re: [DISCUSS] trunk release?
>
> Hi Chris,
>
> On Thu, Nov 22, 2012 at 5:43 PM, Mattmann, Chris A (388J)
> <ch...@jpl.nasa.gov> wrote:
> > "Release early, release often" :)
>
agree + 1
> +1
>
> > Happy Thanksgiving (even though you're not in the States yet)!
>
> Aye, it should have been the other way around. Don't worry it will be
> Burns Night on January 25th.. I'll celebrate from a distance.
>
> Lewis
>
Re: [DISCUSS] trunk release?
Posted by Lewis John Mcgibbney <le...@gmail.com>.
Hi Chris,
On Thu, Nov 22, 2012 at 5:43 PM, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> "Release early, release often" :)
+1
> Happy Thanksgiving (even though you're not in the States yet)!
Aye, it should have been the other way around. Don't worry it will be
Burns Night on January 25th.. I'll celebrate from a distance.
Lewis
Re: [DISCUSS] trunk release?
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
"Release early, release often" :)
I'd say I'd be happy to try and spin it, but you'd beat me to it so I just
will say I'll be happy to test the RC and voice my VOTE when you roll
it Lewis :)
Happy Thanksgiving (even though you're not in the States yet)!
Cheers,
Chris
On Nov 22, 2012, at 7:15 AM, Lewis John Mcgibbney wrote:
> Hi All,
>
> A while ago I asked if it was time to get another release of trunk...
> Markus expressed the valid opinion that there were some issues with
> recently committed material that had maybe not been given the chance
> to mature enough and that could do with more testing.
>
> So far in trunk (since 1.5.1), we've resolved some 45 issues [0], but
> we have some critical issues open [1] which could do with some
> attention as well.
> None of these issues are mine therefore I don't know how those of us
> feel (with patches available) about integrating these issues
> prior/post 1.6 release... or indeed whether a 1.6 release is welcomed
> at the moment? The codebase seems to be stable and getting better so
> from my perspective I would back a 1.X release.
>
> All the best for now
>
> Lewis
>
> [0] http://tinyurl.com/cf3vcpr
> [1] http://tinyurl.com/d4omnrc
>
> --
> Lewis