On 07/11/2011, at 8:43 AM, Jason van Zyl wrote: > You guys decided you wanted to wait so let's just wait. I didn't think it > would take this long to get through either but it is what it is. So > realistically we're looking at 3.0.4 in 4 weeks.
But it could also be longer. I don't see why we should treat the existing EPL release any differently than if it were to be released from Eclipse at this point. Going to Eclipse is a positive step from now, there will be better transparency and governance, but arriving there is not the end of the road. It's going to be even longer that it is more diverse, graduates the incubator there, and becomes just consumable as a dependency. If someone wants to do a 3.0.4 release, they should do it, whether that doesn't include this fix, or delivers it as a patch on the version we're using, or uses the EPL version from Github. If nobody is prepared to do a release now, that's fine too, but they shouldn't have to sit around waiting. The whole reason I was concerned about Aether in the first place was because we'd get stuck not being able to ship a fix to Maven without getting around another project - we can't let ourselves get into that position. In my ideal world, Benjamin would cherry-pick the fix he's already made for the issue Mark is concerned about, release 1.11.1, and we upgrade and someone releases Maven 3.0.4. That wouldn't take long, wouldn't change the direction everything is going, and let everyone get on with it. Is there a reason we shouldn't do that? Cheers, Brett -- Brett Porter [email protected] http://brettporter.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
