On 29/12/2009, at 1:39 PM, Brian Fox wrote: > Is there anything pressing that calls for a 2.2.2? The 3.0's are > moving along and are quite usable.
I was just thinking of shipping the existing fixes and anything obvious or regressed in 2.2.1. On 29/12/2009, at 1:44 PM, Jason van Zyl wrote: > I think that the 3.x code is far enough along that if anyone is going to do > any work I think that enough work has been done in 3.x to stop working on 2.x. > > So much has been fixed, tested and tuned that at this point after using 3.x > for a long time and with the tests that are in place that I'd really like to > flatten all the 2.x versions in JIRA and toss them into the 3.x bucket. Then > scour the issues and just throw out anything that remotely looks like > garbage, close things out and get people to test against 3.x and try and get > the issue count down to the nuggets that are really going to be new features > or are really bugs. Might as well, that's realistically the situation anyway. Nobody is going to do major work on 2.x faced with uncertain prospects in porting it over to 3.x. Keep anything purely specific to 2.x in the 2.2.x bucket and move bigger stuff out. But we have to be 100% focused on shipping 3.0 if that's the case. You can't put an end to 2.2.x when there's no end in sight to 3.0. JIRA needs to reflect exactly what needs to be done for 3.0-alphas, betas and final so we can start counting down. It's fair enough to not specify a date, but at least the target needs to be in sight to get anyone inclined to help with polishing work. For example, where are the issues that reflect switching to Guice and OSGi that we keep hearing about? I just added one for slf4j that you mentioned. What other things are planned that are not in there so we can drive towards a goal? I'd also avoid planning 3.1 alphas at this stage. Focus on getting 3.0 out, and everything else that is after 3.0 can be up for grabs. > > There are ~650 issues and I think in four weeks with a little teamwork we can > probably drive that down to the 50 things we care about. I'm happy to help clean up issues, sure. I make a small dent in it occasionally, but it tends to sap any energy before starting to do any actual work. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
