To reply to your original point Markus, I agree with your suggestion. It occured to me recently that although many smaller issues apply to both branch 1.4 and trunk 2.0, the methods required to implement them on many occasions are different from a coding perspective therefore require different time allocated for resolution. Differentiating between the job requirements for both branch and trunk would give whoever working on the problem (and anyone viewing the JIRA ticket) a clearer outlook on the current state of play.
On Thu, Jun 30, 2011 at 11:12 AM, Julien Nioche < [email protected]> wrote: > > I'd be happy to roll 1.4 whenever we're ready. >> > > There are quite a few things that we've discussed for 1.4 (e.g. make > indexing backend plugable, delegate code to crawler-commons) so it is a bit > premature to talk about releasing 1.4 just now. End of 2011 would be a good > deadline, with a release roughly every 6 months > > Julien > > >> >> 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 >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> > > > -- > * > *Open Source Solutions for Text Engineering > > http://digitalpebble.blogspot.com/ > http://www.digitalpebble.com > -- *Lewis*
