Dear Wiki user, You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification.
The following page has been changed by TedHusted: http://wiki.apache.org/struts/StrutsActionRelease200 The comment on the change is: Move 2.0.0 release plan to Confluence wiki ------------------------------------------------------------------------------ - = Struts 2.0.0 Release = + [http://cwiki.apache.org/confluence/display/WW/Release+Plan+2.0.0 THIS PAGE HAS MOVED.] - * Struts 2.0.0 is preparing a "early adopter" build. - * Codebase seems feature-complete. - * Documentation issues remain. - * Example issues remain. - * Assembly/distribution issues remain. - See also [https://issues.apache.org/struts/secure/IssueNavigator.jspa?mode=hide&requestId=10681 Struts 2.0.0 TODO] in the issue tracker. - - == Overall Status == - - || Initial rename of packages and configuration files || Complete || - || Pass Web``Work2 codebase through the Incubator || Complete || - || [http://issues.apache.org/struts/browse/SITE-3 Setup Nightly Builds] || Pending || - || [http://issues.apache.org/struts/browse/WW-1340 Update WW2 documentation for Struts 2] || Step 3 of 4 || - || [http://issues.apache.org/struts/browse/WW-1341 Utilize Cookbook format for Showcase and add Struts-Examples use cases] || - || - || [http://issues.apache.org/struts/browse/WW-1342 Remove deprecated members (IoC components)] || Complete || - || [http://issues.apache.org/struts/browse/WW-1343 Deprecate selected legacy API members (e.g. Around``Interceptor, "do" clause)] || Complete || - || [http://issues.apache.org/struts/browse/WW-1344 Update Javadoc to match new package and configuration naming] || Complete || - || Implement selected new features and Struts 1 features (infra) || Complete || - || [http://issues.apache.org/struts/browse/WW-1345 Add Struts 1 and WW2 Migration Guides] || Initial draft added || - || [http://issues.apache.org/struts/browse/WW-1346 Develop routine for exporting wiki to HTML/PDF] || Pending || - || [http://issues.apache.org/struts/browse/WW-1378 Develop Maven assembly to create distribution] || Pending || - || Second documentation review || - || - || Complete standard release plan || - || - || - || - || - - == Documentation Status == - - [http://confluence.twdata.org/display/WW/Home Confluence Space] - - || Step 1 - Setup new Confluence instance || Complete || - || Step 2 - Initial pass to update nomenclature and remove obsolete material || Complete || - || Step 3 - Update "snippets" to reference ASF repository || Pending || - || Step 4 - Complete tutorials and other "TODO" sections || Pending || - - == Info == - - 1. Apache Struts [http://struts.apache.org/releases.html#Releases Release Guidelines] - - 2. [http://wiki.apache.org/incubator/SigningReleases Signing Releases] - - 3. Apache [http://apache.org/dev/mirrors.html Mirroring Guidelines] - - == Release Manager == - - The release manager is '''Ted Husted'''. - - == See Also == - - * [http://issues.apache.org/struts/browse/WW-1349 Struts 2.0.0 omnibus ticket] - * [http://issues.apache.org/struts/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10030&fixfor=21510 Issue Tracker] - * [http://wiki.apache.org/struts/StrutsTi Struts Ti Proposal] - * [http://wiki.apache.org/struts/StrutsAction2 Migration Issues] - * [http://wiki.apache.org/struts/RoughSpots Struts 2 Rough Spots] - * [http://svn.apache.org/viewcvs.cgi/struts/action2/trunk/action-api Public API Whiteboard] - * [http://retroweaver.sourceforge.net/documentation.html Retroweaver] - - == Special Issues == - - Struts 2.0 is based on the Web``Work 2.2 codebase. Essentially, Struts 2.0 will be the technical equivalent of Web``Work 2.3. (The Web``Work2 codebase was accepted into the Struts project through the [http://incubator.apache.org/projects/webwork2.html Apache Incubator].) - - For Struts 2.0, the core goals are to repackage the codebase as an Apache Struts product and to provide migration resources for Struts 1 and WW 2 developers. A few legacy API elements will be removed, and a few new features will be added. - - The Struts 2.0 release is following the [http://wiki.apache.org/struts/StrutsTi Struts Ti Proposal]. Struts 2.0 is Phase 1 of the proposal. A subsequent Struts release series (either Struts 2.1 or Struts 3.0) will address Phase 2 of the proposal. - - Struts 2.0.0 is targeting August 2006 as a relaxed release date. - - The platform for Struts 2.0.x is Java 1.5, with Java 1.4 compatibity provided by [http://retroweaver.sourceforge.net/documentation.html Retroweaver]. - - See also [StrutsAction2 Struts 2]. - - == New Features Under Consideration == - - This initial list of new features is taken from the [http://wiki.apache.org/struts/RoughSpots SAF2 Rough Spots] page. - - Review and Refinement - - * Separate classes that most applications need to use. Isolate classes that the framework uses internally or that are rarely used by applications. (See Rough Spot #3.) - * Distinguish between the published public versus private APIs. (See Rough Spot #4.) - * Utilize properties (methods) instead of protected or public fields (). (See #13.) - * Review exception handling. Some are still being swallowed rather than rethrown. (See #20 and [http://issues.apache.org/struts/browse/WW-652 WW-652]) - - Modifications - - * Simplify Text``Provider. (See #15.) - * Modify `ParametersInterceptor` to sort parameter names by depth (using bucket sort) and then map them in that order (shallowest first). (See #21.) - * Use the strategy pattern to swap in different implementations of interfaces like Validation``Aware. (See Tim, NTH #1.) - - [http://issues.apache.org/struts/browse/WW-1343 Deprecations and Removals] - - * Deprecate or remove the Around``Interceptor. (See #7.) - * Eliminate "do" clause for Action alias lookups. Scan Actions at load time for known aliases, and fail fast. - - Architecture - - * Address the confusing issue of the validation/workflow lifecycle and different methods. (See Patrick #4.) - - Configuration - - * Add support for type aliasing (a la Spring and iBATIS) to reduce or eliminate need to use fully-qualified class names, over and over. The fully-qualified type is declared once, and then a simple type "nickname" can be used instead. (See #23.) - * Combine configuration DTDs so that Actions, Messages, and Validators can be defined in a single file. (See Ted, #1.) - * Use values on the stack to override/define configuration options. (See Tim, NTH #3.) - - OGNL - - * On the OGNL value stack, rename #request for request parameters and #requestAttributes for request attributes. (See #17 and [http://issues.apache.org/struts/browse/WW-785 WW-785].) - * Work with OGNL to add Java 5 support. (See #31.) - * Work with OGNL to make it a clear superset of JSTL. (See Gabe #4.) - - == Struts 1 Features to Implement == - - [http://issues.apache.org/struts/browse/WW-1347 JIRA issue] - - * Wildcard Action Mappings (Done in XWork 2) - * Dyna``Form as Model Object (including [http://forums.opensymphony.com/thread.jspa?messageID=67350𐜖 LazyDynaForms]) - * Extends for action mappings (See Tim, NTH #2.) - * Change the default submit method for the form tag from GET to POST (See Ted, #2.) - * [http://issues.apache.org/struts/browse/WW-1350 Set field focus] - - ---- - - == Outstanding Issue Review == - - [http://issues.apache.org/struts/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10030&fixfor=21510 Struts 2.0.0 Issues] - - == Preparation Checklist == - - || '''#''' || '''Description''' || '''Status''' || - || 1. || ${DESCRIPTION} || ${STATUS} || - - The Commons [http://jakarta.apache.org/commons/releases/prepare.html Preparation Guide] is a helpful preparation backgrounder, but Commons uses the "beta/release-candidate/final" process. Likewise, the [http://httpd.apache.org/dev/release.html HTTPD Release Guidelines] is a helpful "overall process" backgrounder, but HTTPD does not use a test-build stage. - - Dependency versions for this release: - - || '''Dependency''' || '''Version''' || '''Status''' || - || ${DEPENDENCY} || ${VERSION} || ${STATUS} || - - == Testing Checklist == - - === Testing Summary === - - || '''#''' || '''Description''' || '''Completed''' || - || 1. || Run Unit Test targets || ${STATUS} || - || 2. || Play test bundled applications || ${STATUS} || - - TODO: A Canoo WebTest for the applications would be great! - - == Test Build Checklist (A) == - - See also Commons [http://jakarta.apache.org/commons/releases/release.html Step-by-Step Guide] - - || '''#''' || '''Description''' || '''Completed''' || - || A1. || Tag release in svn: ${STRUTS_x_x_x} || ${STATUS} || - || A2. || Run Distribution Target || ${STATUS} || - || A3. || Upload Distribution to svn.apache.org:/www/svn.apache.org/dist/struts/x.x.x || ${STATUS} || - || A4. || Post release-quality vote on dev@ lists || ${STATUS || - - == Vote (A) == - - || ${PMC_MEMBER} || ${GRADE} || - - * If release vote fails, including for a lack of quorum, remove from dist folder. - * If a release vote passes (Alpha, Beta or GA), the release may be announced and mirrored. - * If vote is GA, goto Checklist (C). - - == Point Release Checklist (B) == - - || B1. || Create Sums and Sign Distributions [2] || ${STATUS} || - || B2. || Setup new JIRA version level or update release on Roadmap || ${STATUS} || - || B3. || Update "Acquiring" page on website and Test Downloads || ${STATUS} || - - == Vote (B) == - - If initial vote is Alpha or Beta, voting can continue until a GA or "withdraw" vote passes, or there is a subsequent release. - - || ${PMC_MEMBER} || ${GRADE} || - - - == General Availability Checklist (C) == - - || '''#''' || '''Description''' || '''Completed''' || - || C1. || Copy Distribution to Mirrored Directories [3] || ${STATUS} || - || C2. || Deploy JAR to Apache Java-Repository || ${STATUS} || - || C3. || After 24 hours, update "Acquiring" page on website || ${STATUS} || - || C4. || Post an announcement to lists and website || ${STATUS} || - - ---- -
