7 messages in org.apache.struts.devRe: committers attention - just a few...| From | Sent On | Attachments |
|---|---|---|
| Arron Bates | Feb 25, 2003 3:02 pm | |
| Karr, David | Feb 25, 2003 3:06 pm | |
| Craig R. McClanahan | Feb 25, 2003 3:25 pm | |
| David Graham | Feb 25, 2003 3:32 pm | |
| Arron Bates | Feb 25, 2003 3:41 pm | |
| David Morris | Feb 25, 2003 9:47 pm | |
| Ted Husted | Feb 26, 2003 5:25 am |
| Subject: | Re: committers attention - just a few moments... | |
|---|---|---|
| From: | Ted Husted (hus...@apache.org) | |
| Date: | Feb 26, 2003 5:25:02 am | |
| List: | org.apache.struts.dev | |
Arron Bates wrote:
Too unstable for 1.1 so close to release, but too important to let it slip for over a year for it to come out.
I agree that you should apply the patch if you are comfortable with it yourself, since working on Tomcat 4.1.18 is important to our community.
I also very sure that people who use the Nested taglib *do* consider it a favorite component, and that there will be *a lot* of traffic if it doesn't work properly =:>
Meanwhile, you're right in thinking that this is a case where it's better to float a proposal for patch first and commit it second. On occaision, it's easier to ask for permission than forgiveness =:0)
But, I don't think it will be so long before Struts 1.2. In fact, as soon as 1.1 ships, I'd like to do just a few of the straggling things, like the resources migration, and get 1.2 out right away.
I'm also convinced that we need to give significant subsystems like Struts-EL, Nested, Struts-JSP (when it happens), Tiles, and the Validator, their own release cycles. So that Struts becomes more like the Commons and less like Turbine.
-T.
-- Ted Husted, Struts in Action <http://husted.com/struts/book.html>