Hi Doğacan,
So your proposition is to combine (a) and (b) then? That’s fine by me, so long
as there are no objections from others. I can still move forward with , (e) and
(g) then...
Cheers,
Chris
On 6/28/10 8:39 AM, "Doğacan Güney" <doga...@gmail.com> wrote:
Hey all,
I will double check to make sure, but IIRC, there is no need to delete
svn:nutchbase since current code on
github simply builds on top of that. So why not simply merge github branch into
svn? It will be a clear merge...
The only problem is contributor info is messed up in github but I tried to
preserve as much contrib info as possible
when I pulled in 1.1 changes (via git cherry-pick). So we can break the code in
github into smaller patches, apply them
on top of svn nutchbase (which, again, will be clean) then, 1.1 changes can be
applied by _original_ committers, thus
hopefully preserving contributor info as well.
Makes sense?
On Mon, Jun 28, 2010 at 16:45, Julien Nioche <lists.digitalpeb...@gmail.com>
wrote:
Hi,
(a) deleting svn:nutchbase
(b) svn:importing Git Nutchbase.
(c) branch current 1.2-trunk as 1.2-branch
(d) iteratively apply patches from new svn:nutchbase to trunk to bring
it up to snuff.
(e) roll the version # in nutch trunk to 2.0-dev
(f) all issues in JIRA should be updated to reflect 2.0-dev fixes where
it makes sense
(g) a 2.1 version is added to mark anything that we don't want in 2.0
and we file post 2.0 issues there
(h) Nutch 2.0 trunk is fixed, and brought up to speed and old code is
removed. All unit tests should pass regression where it makes sense.
(i) Nutch documentation is brought up to date on wiki and checked into
SVN
(j) We roll a 2.0 release
+1
I'd be happy to do (a), (c), (e) and (g) tomorrow, and would like to
participate in (d) and (f).
I'm thinking Julien and Doğacan would be the
best people to do (b) and (i).
Doğacan is in the process of writing the documentation
(h) should be a result of all steps prior
(a)-(g), and as for (j), I'd be happy to do (j) when the time comes.
So, if I don't hear any objections, I'll do (a), (c), (e) and (g)
tomorrow... (6/28, likely PM PST Los Angeles time)
cool, thanks
J.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
