> Currently we have three versions of nutch: trunk, 0.7 and mapred. > This > increases the chances for conflicts. I would thus like to merge the > mapred branch into trunk soon. The soonest I could actually start > this is next week. Are there any objections?
I, too, am looking forward to this, but I am wondering what that will do to Kelvin Tan's recent contribution, especially since I saw that both MapReduce and Kelvin's code change how FetchListEntry works. If merging mapred to trunk means losing Kelvin's changes, then I suggest one of Nutch developers evaluates Kelvin's modifications and, if they are good, commits them to trunk, and then makes the final pre-mapred release (e.g. release-0.8). Otis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simpy -- http://www.simpy.com/ -- Find it. Tag it. Share it. ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Nutch-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nutch-developers
