IMO, FWIW ... Ted Husted <[EMAIL PROTECTED]> wrote on 09/03/2004 07:11:48 AM:
> OK, to sum up what people seem to be saying here: > > [Struts 1.2.x] > > * The minimums for 1.2.3 will remain Servlet 2.2 > > * We create a branch at the 1.2.3 tag, in case we need to make > critical fixes to 1.2.x later. > +1 > [Struts HEAD] > > * For now, Struts HEAD can remain in evolutionary mode, but we will > bump the minimum to Servlet 2.3. At this point in time, this seems > like a minor change, and so for the purposes of the Roadmap, we > could assume the next release will be 1.3.0. But the final decision > is up to the PMC when there's something to ready to release. ( > +1 > * If anyone on the PMC feels strongly about the versioning, we can > change all the markers on the Roadmap, so features slotted for 1.3.x > ascribe to 2.0.x, and so forth, but that seems like a lot of churn > for little benefit > > * Some of the reasons we are moving to Servlet 2.3 are: > > * It is preferred platform of active Struts developers. > * It is needed for certain enhancements, including some to file upload. > * It simplifies distribution and integration of JavaServer Faces > components which are dependant on Servlet 2.3. > Agree. > * If at any time, we decide to move the HEAD to revolutionary mode, > so as to stretch or break backward-compatibility, we can branch > again, and assume that the HEAD will become 2.0.0 at the next > release. But, we don't have to make that decision until a > revolutionary commit is pending :) > +2 > * So far, items like Struts Chain count as evolutionary, since it > seems we will be extending the API to support other "Action" > signatures (e.g. for Portlets), but not removing the old ones. (As > we did when we changed the signature for Exception handling.) > > [Struts NEXT] > <snip/> Susan Bradeen _____________________________________________________________________________ Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs. _____________________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
