If everything else is resolved, I don't think we need to wait on Validator 1.1.4. If it's ready when we are, fine. If not, #18169 does not seem like a "showstopper" issue to me, and we can finish implementing the feature in the 1.3.x series.
I'm trying to resolve the issues not listed as "outstanding" on the release plan, which should put us in a position to roll 1.2.6. I would be in favor of immediately branching at 1.2.6, regardless, so we can start on 1.3.x. If there are any straggling issues with the 1.2.x build, I'd be happy to cross-commit between the 1.2.x and 1.3.x branches. We've let 1.2.x block 1.3.x long enough, and it's time to "move on to bigger and better things". We did tag and roll 1.2.5, it just didn't go anyplace, which is going to happen now and again. -Ted. On Thu, 18 Nov 2004 08:21:30 -0600, Joe Germuska wrote: >> Seams that Chain is only for Struts 1.2 ? >> or 1.3, which is based on Servlet2.2 >> > I believe that we reached consensus that it would be ok to move > Struts 1.3 to depend on Servlet 2.3. Work on Struts 1.3 is blocked > on the release of a GA 1.2.x Struts so as to minimize any need to > apply patches across both branches. > > Looking at http://wiki.apache.org/struts/StrutsRelease126, is it > true that we are just waiting for commons-validator 1.1.4 to be > marked "GA"? The other bugs all seem to be marked for 1.3 except > one which is underspecified. > > Should we somehow annotate this page: > http://wiki.apache.org/struts/StrutsRelease125 to indicate that > there isn't going to be a 1.2.5 release? Or should we have a vote > on it even though 1.2.6 is brewing? > > Joe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
