nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sebastian Nagel <wastl.na...@googlemail.com>
Subject Re: [DISCUSS] Release Trunk
Date Fri, 14 Feb 2014 15:31:33 GMT
Hi,

-1 also from me for now.

Beside SegmentMerger (NUTCH-1113) there is a problem in indexer (NUTCH-1706/NUTCH-1646)
which should be fixed. I hope to tackle both issues soon.

Sebastian


On 02/13/2014 10:19 AM, Markus Jelsma wrote:
> Seems some of my mails to the list are not coming through. I am -1 on release from trunk
as is. The segment merger is still broken and in my opinion we cannot push yet another release
with a broken segment merger.
> 
> Markus
> 
> -----Original message-----
> From: Tejas Patil<tejas.patil.cs@gmail.com>
> Sent: Thursday 13th February 2014 1:33
> To: dev@nutch.apache.org
> Subject: Re: [DISCUSS] Release Trunk
> 
> Just saw the commits since 1.7 release. Apart from trivial bug fixes, we have some significant
patches since 1.7.
> 
> +1 for new release. I would be happy to volunteer / help.
> 
> Thanks,
> 
> Tejas
> 
> On Wed, Feb 12, 2014 at 7:33 AM, Julien Nioche <lists.digitalpebble@gmail.com <mailto:lists.digitalpebble@gmail.com>>
wrote:
> 
> Hi guys,
> 
> At least 2 of the issues that Seb and I had mentioned have now been committed. What about
releasing 1.8 from trunk? If so, any volunteers?
> 
> Julien
> 
> On 2 December 2013 21:02, Sebastian Nagel <wastl.nagel@googlemail.com <mailto:wastl.nagel@googlemail.com>>
wrote:
> 
> Hi,
> 
> +1 to release soon (this year, or early next year)
> 
>> and probably a few others but they could also be done later.
> 
> At least, these should be done before releasing:
> 
> NUTCH-1646 IndexerMapReduce to consider DB status
> 
> NUTCH-1413 Record response time
> 
> Sebastian
> 
> On 11/28/2013 05:49 PM, Julien Nioche wrote:
> 
>> Hi Lewis
> 
>>
> 
>> Weve done quite a few things in 1.x since the previous release (e.g. generic deduplication,
> 
>> removing indexer.solr package, etc...)  and the next 2.x release will be after the
changes to GORA
> 
>> have been made, tested and used on the Nutch side so that could be quite a while.
> 
>>
> 
>> I am neutral as to whether we should do a 1.x release now. There are some minor issues
that we could
> 
>> do in 1.x before the next release like :
> 
>> * https://issues.apache.org/jira/browse/NUTCH-1360 <https://issues.apache.org/jira/browse/NUTCH-1360>
> 
>> * https://issues.apache.org/jira/browse/NUTCH-1676 <https://issues.apache.org/jira/browse/NUTCH-1676>
> 
>> and probably a few others but they could also be done later.
> 
>>
> 
>> Lets hear what others think.
> 
>>
> 
>> Thanks
> 
>>
> 
>> Julien
> 
>>
> 
>>
> 
>>
> 
>>
> 
>> On 28 November 2013 16:34, Lewis John Mcgibbney <lewis.mcgibbney@gmail.com <mailto:lewis.mcgibbney@gmail.com>
> 
>> <mailto:lewis.mcgibbney@gmail.com <mailto:lewis.mcgibbney@gmail.com>>>
wrote:
> 
>>
> 
>>     Hi Folks,
> 
>>     Thread says it all.
> 
>>     There are some hot tickets over in Gora right now so I think holding off the
next while for a
> 
>>     2.x release would be wise.
> 
>>     I can spin the RC for trunk tonight/tomorrow/weekend if we get the thumbs up.
> 
>>     Ta
> 
>>     Lewis
> 
>>
> 
>>     --
> 
>>     /Lewis/
> 
>>
> 
>>
> 
>>
> 
>>
> 
>> --
> 
>> *
> 
>> *Open Source Solutions for Text Engineering
> 
>>
> 
>> http://digitalpebble.blogspot.com/ <http://digitalpebble.blogspot.com/>
> 
>> http://www.digitalpebble.com <http://www.digitalpebble.com>
> 
>> http://twitter.com/digitalpebble <http://twitter.com/digitalpebble>
> 
> --
> 
> Open Source Solutions for Text Engineering
> 
> http://digitalpebble.blogspot.com/ <http://digitalpebble.blogspot.com/>
> 
> http://www.digitalpebble.com <http://www.digitalpebble.com>
> http://twitter.com/digitalpebble <http://twitter.com/digitalpebble>
> 
> 


Mime
View raw message