Am Mi, 22.08.2007, 16:51, schrieb Ted Husted: > I expect that we would want to move anything for 2.0.10 (resolved or > not) to 2.1.0, and anything slated for 2.0.11 to 2.1.1. >
-1 for moving any issue now. 2.1 is not a simple drop in replacement for 2.0.x AFAICS. I would expect a (hopefully short time) where the 2.0.x tree still might need maintainance, unless 2.1 has proved itself in the wild. I think the the first few months since a release of 2.1 there still be lots of users staying with 2.0.x, and we might want to push out one or more versions (although this does not _have_ to be the case). That said, I would vote for not moving for _all_ tickets now, thus not losing information. Since I'm working myself on customer projects depending on 2.0.x at least the next few months, I'll keep on helping to maintain / backport the most needed features / issues in 2.0.x tree (I'm currently backporting & testing the Servlet-Portlet wrapping mechanism). For the testing of a 2.1 release, I'll be happy to test some of the said customer projects against it. Regards, Rene --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
