>
>  Before doing so,
>> let's:
>>
>> 1. tag current trunk as
>> http://svn.apache.org/repos/asf/nutch/branches/branch-1.3 (EOL'ed won't
>> be
>> worked on, but nice to save). This way someone doesn't have to remember
>> the
>> Nutchbase rev # before the Nutchbase branch lands in the trunk.
>>
>> Then we can:
>>
>> 2. svn remove -m "n-1 before Nutchbase lands."
>> https://svn.apache.org/repos/asf/nutch/trunk
>> 3. svn copy -m "Nutchbase branch lands in trunk."
>> https://svn.apache.org/repos/asf/nutch/branches/nutchbase
>> https://svn.apache.org/repos/asf/nutch/trunk
>>
>> After doing that, we should also:
>>
>> 4. roll a a 1.2 release, which I would say is the last major 1.x release.
>> Andrzej and I and others have backported some pretty decent patches in the
>> past few weeks and it probably makes sense to make a quick release. I'll
>> happily be the RM for it.
>>
>
> +1 to all of the above - see below.
>
>
>
>> So if 1-4 make sense, let's do 1, 2 and 3 today or tomorrow -- 4 can
>> happen
>> over the next few weeks. WDYT?
>>
>
> This is a serious move - let's wait a bit, say until Monday, to give chance
> to others to comment.
>

+1 from me as well

Julien

-- 
DigitalPebble Ltd

Open Source Solutions for Text Engineering
http://www.digitalpebble.com

Reply via email to