> > Failing responses from people who are actually familiar with the nested > > tags and your changes, then I think you'll just have to use your own > > judgment. I had to make a similar decision recently wrt the Struts-EL > > tags. Test your changes as much as possible, and try to get some > > feedback from people who are using your tags. If you think it's safe to > > commit, then do it (but don't quote me on that :) ). > > > > David > > I think David articulates a rational approach. If you think the fix for > nested tags should go in (in spite of being a larger patch than we might > be normally comfortable with), and you've tested it as much as you can, > I'm certainly not going to argue. Worst case - we do an RC2 with this fix > to give the world one more shot at proving it's still got a problem. > > Craig >
This is the feedback I'm after. Had I simply committed the patch that is on the big side, I would have been trounced. Especially seeing that time hasn't let me play apache recently, to then walk in and make such a large play (on RC1 day no less). Wouldn't have gone over well I imagine. Arron. BTW: So far, none of the early adopters have said their apps have broken with the new changes. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
