No objections form me. We waited long and we can fix things in
maitenance release in few weeks.
Regards
Piotr

On 7/26/06, Sami Siren <[EMAIL PROTECTED]> wrote:
> Andrzej Bialecki wrote:
>
> > Sami Siren wrote:
> >
> >> There is a package available for testing in
> >> http://people.apache.org/~siren/nutch-0.8/
> >>
> >> please give it some testing and post in your opinion - is it good
> >> enough to be a public release?
> >>
> >> I have some doubts because of NUTCH-266, but so far only 3 people
> >> have reported this to be problem
> >> (me included)
> >
> >
> > This is I guess related to a very specific environment - multiple
> > nodes running on cygwin. Usually people run multiple nodes on some
> > flavor of Unix.
> >
> > I don't have any means to test it for this issue ...
> >
> Bug also appears in singlenode configuration, but I think that it is not
> that common (quessing from the number of people who have reported it).
> However that is now fixed in hadoop trunk. Should we use a patched
> version of hadoop-0.4.0 in Nutch or wait for 0.5 (which at least still
> seems to be 1.4 compatible)?
>
> The 0.8 package has now hit the mirrors, has anybody any objections
> about announcing it? Stefan allready commented about two issues he
> wished to be fixed in 0.8 but to me it looks that they can both be
> addressed with configuration changes and documentation in the first
> place and there's nothing stopping us from releasing 0.8.1 in very short
> time addressing the issues discovered in 0.8.
>
> --
>  Sami Siren
>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Nutch-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nutch-developers

Reply via email to