Hey Guys, On 6/29/10 2:30 AM, "Andrzej Bialecki" <a...@getopt.org> wrote:
>> I am probably missing an important point here, but if so I would >> appreciate if someone (Dogacan?) could explain why we should not stick >> to the original plan >> (a) clear the existing svn nutchbase >> (b) generate a large patch with the code from github and JIRA it >> (c) commit the changes to svn nutchbase >> then get on with the interesting bits. Like I said, whether we merge the Github Nutchbase into the Apache Nutchbase branch or we blow away the Apache Nutchbase branch and then import the Github Nutchbase branch wholesale, either way, we are left with an Apache Nutchbase branch that needs to incrementally be merged into the Nutch 2.0 trunk, which I agree with Andrzej, and Julien, is the most important part. So, either way works fine with me, so long as we are left with an Apache Nutchbase branch that can be merged incrementally with the Apache Nutch 2.0 trunk. I'm just not going to be the one doing that first part (Github transfer), so I didn't want to push one way or another. Once the Apache Nutchbase branch is ready, can we identify a set of 5-10 JIRA patches that we can use to track how to bring the Apache Nutchbase branch into the Apache Nutch 2.0 trunk? At that point, I'll likely be of use again :) Until then, Julien, Dogacan, I think the floor is yours. Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.mattm...@jpl.nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
