hi, > +1 to creating separate issues (and sorry for the extra work it creates!)
It's only a minor task for issues ready to commit for 1.4. > > I'd be happy to roll 1.4 whenever we're ready. That's always good news but there are some issues in 1.4 that require more devs to look at, esp https://issues.apache.org/jira/browse/NUTCH-1014 and related issues. Cheers > > Cheers, > Chris > > On Jun 30, 2011, at 6:25 AM, Markus Jelsma wrote: > > Hi, > > > > Some issues have been resolved for 1.4. There may be a patch for 2.0 but > > these remain untested and are not committed so the issues remain open. > > Should i create seperate issues for 2.0 for issues that are not > > immediately going to be implemented and tested for 2.0? If so, i can set > > commits for 1.4 to resolved and have a clean list of issues for 1.4. > > > > Thoughts? > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Chris Mattmann, Ph.D. > Senior Computer Scientist > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 171-266B, Mailstop: 171-246 > Email: [email protected] > WWW: http://sunset.usc.edu/~mattmann/ > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Adjunct Assistant Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
