The Apache Project

Objective

$Id: release-plan-1.1b3.xml 51063 2003-09-09 17:49:23Z sraeburn $

The objective of the Struts 1.1 Beta 3 release is to create a milestone release against which a final series of bug fixes and documentation updates can occur before a Struts 1.1 Final release is created.

The Plan

A number of new features have been added to the nightly builds since the second Beta release of Struts 1.1, and many bugs have been fixed. It is time, therefore, to take the next step in the release process, and make the latest code base available as a third Beta release. The goal is to move towards a release candidate and then a final Struts 1.1 release as soon as is practicable.

Therefore, the following release plan is proposed for Struts 1.1 Beta 3:

  • Code Freeze / Tag Date - Sunday, December 29, 2002, 23:59:59
  • Release Manager - Martin Cooper
  • Release Announcement - To the following mailing lists:
    • announcements@jakarta.apache.org
    • struts-dev@jakarta.apache.org
    • struts-user@jakarta.apache.org

Release Criteria

Prior to the release of Struts 1.1 Beta 3, the following action items must be completed:

  • The Struts 1.1 Release Notes document shall be updated to describe substantial changes and improvements since the Struts 1.0.2 release, along with associated updates to the main Struts Documentation Application pages describing the new release.
  • All of the Struts example applications that are included with the release shall operate successfully in the following servlet containers:
  • A release vote shall take place on the STRUTS-DEV mailing list to approve this plan. The release vote MUST pass by "Majority Approval" of Struts committers.

Prior to the release of a subsequent Struts 1.1 release candidate, the following action items must be completed:

  • All Bugzilla bug reports against Struts 1.1 nightly builds MUST be marked as "Resolved", with any of the legal Bugzilla resolutions (FIXED, INVALID, WONTFIX, LATER, REMIND, WORKSFORME).
  • Bug reports that are resolved as LATER or REMIND will include comments as to whether those specific issues will be dealt with in a subsequent beta, release candidate, or final release, or whether they will be scheduled for consideration in a subsequent release time frame.

Bugs To Be Addressed

The following bugs must be addressed before Final Release of Struts 1.1. Checked items have been resolved.

Custom Tags
[x] 11021 ActionForward or <html:link> tag does not support absolute URIs
[x] 12302 Sporadic error in html:form action attribute
[x] 13645 Add action attribute to <html:link>
[x] 15044 Taglib - Index Attribute in html:Checkbox doesn't set correctly
[x] 15196 Bug on the RequestUtils.computeParameters using a DynaValidatorForm as map of the parameter
[x] 15451 Multiple mapped properties not possible / Direct maps and indexes not possible
[x] 15601 tile examples to move to standard webapp location
Controller
[x] 12871 ExceptionHandler does not obey controller inputForward rule
[x] 14054 Rename "Application" components to "Module"
[x] 14749 Action "input" not starting with '/' and not a valid forward will cause an internal server error
Documentation
[x] 10537 [:TODO:] sections
[x] 15167 Updated Action documentation
Utilities
[x] 11932 (Message Resource is not multi-app aware) Multi-Resource not work in Multi-Appliction config environment
Unknown
[x] 14042 Unknown Memory leaks with JBoss 3.x +(Tomcat/Jetty)
Post Mortem -- These tickets were added after the release of Struts 1.1 B3 and need to be resolved before the next iteration
[x] 15736 Struts doesn't initialize under strict security manager
[x] 15799 Nested tags picks up wrong bean for values
[x] 15883 wrong resource file used in multi-application context
[x] 16019 LookupDispatchAction multiple MessageResources
[x] 16514 NestedtTiles fail in this release
[x] 16603 internalModuleRelativeForward() doesn't treat module-relative paths as defined by forwardPattern
[x] 16609 MessageResource not in request scope for Module