Struts Extras 1.3.1 Release
Info
Struts Release Guidelines
Apache Mirroring Guidelines
Release Manager
The release manager is Wendy Smoak
How to Help
Everyone in the Struts community, users, developers, and committers, is encouraged to test a release, report any issues, and post to dev@ any comments on the overall quality of the release.
To help everyone get started with Struts Extras 1.3.1 (when it is available), here are the simplest installation instructions that can possibly work:
Download the Struts Extras 1.3.1 distribution from http://svn.apache.org/dist/struts/extras/v1.3.1/ (when it is available)
- Extract subproject distribution to a likely location (\opt\struts-*)
- Install Java and set JAVA_HOME
- Install Maven and set MAVEN_HOME
- Install the Cactus Plugins and Apache Tomcat
- Change to the Struts Build folder (e.g., \opt\struts-build)
- $ maven
- Wait about five minutes for Maven to download and build everything
* If you see any error messages, see if they are known issues by comparing your log with ours at http://svn.apache.org/builds/struts/maven/trunk/nightly/logs/
Outstanding Bug Review
ID |
Summary |
Status |
Replacement of LookupDispatchAction |
WONTFIX (superceded by 38343) |
|
Added EventActionDispatcher |
Patch Applied. |
|
XSS vulnerability in LookupDispatchAction |
Fixed |
Preparation Checklist
# |
Description |
Status |
1. |
Announce plan to dev@ list or update Wiki page |
|
2. |
Review/Resolve Outstanding Bugs |
_ |
3. |
Update Release Notes |
_ |
4. |
Check Dependencies |
_ |
5. |
Update to version 1.3.1 project.xml, pom.xml |
_ |
The Commons Preparation Guide is a helpful preparation backgrounder, but Commons uses the "beta/release-candidate/final" process.
Likewise, the HTTPD Release Guidelines is a helpful "overall process" backgrounder, but HTTPD does not use a test-build stage.
External Dependency versions for this release:
Dependency |
Version |
Status |
Used In |
Antlr |
2.7.2 |
Released |
Struts Validator |
Commons BeanUtils |
1.7.0 |
Released |
core (ActionServlet, configuration, DynaActionForm) |
Commons Chain |
1.0 |
Released |
core (RequestProcessor) |
Commons Digester |
1.6 |
Released |
core (ActionServlet, configuration) |
Commons FileUpload |
1.0 |
Released |
Struts Upload |
Commons Logging |
1.0.4 |
Released |
core (logging all over) |
Commons Validator |
1.1.4 |
Released |
Struts Validator |
Jakarta Oro |
2.0.8 |
Released |
Commons Validator |
Testing Checklist
Testing Summary
# |
Description |
Completed |
1. |
Run Unit Test targets |
_ |
2. |
Run Cactus Tests (see below) |
_ |
3. |
Play test bundled applications (TC 5.0.x) |
_ |
Cactus Tests
# |
J2SE Version |
Tomcat Version |
Status |
1. |
J2SE 1.3.1_04 |
Tomcat 4.1.30 |
_ |
2. |
J2SE 1.4.2_07 |
Tomcat 4.1.30 |
_ |
3. |
J2SE 1.3.1_04 |
Tomcat 5.0.28 |
_ |
4. |
J2SE 1.4.2_07 |
Tomcat 5.0.28 |
_ |
Test Build Checklist (A)
See also Commons Step-by-Step Guide
# |
Description |
Completed |
A0. |
Update extras and build, project.xml and pom.xml to omit "-SNAPSHOT" |
_ |
A1. |
Tag release in svn: STRUTS_EXTRAS_1_3_1, STRUTS_BUILD_1_3_x |
_ |
A1.1 |
Modify svn:externals for 'build' on STRUTS_EXTRAS_1_3_1 tag |
_ |
A2. |
Check out a clean copy using the tag created in A1 and and run Distribution Target |
_ |
A3. |
Upload Distribution to cvs.apache.org:/www/cvs.apache.org/dist/struts/taglib/v1.3.1 |
_ |
A4. |
Post release-quality vote on dev@ and user@ lists |
_ |
A5. |
Update taglib and build, project.xml and pom.xml to "1.3.x-SNAPSHOT" |
_ |
Vote (A)
PMC Member |
Quality |
Voting thread is _
If release vote fails, including for a lack of quorum, remove from dist folder.
Point Release Checklist (B)
# |
Description |
Completed |
B1. |
Create Sums and Sign Distributions [2] |
_ |
B2. |
Request new Bugzilla version level (1.3.1) |
_ |
B3. |
Update "Acquiring" page on website and Test Downloads |
_ |
Vote (B)
PMC Member |
Quality |
Voting continues until a GA or "withdraw" vote passes, or there is a subsequent release.
General Availability Checklist (C)
# |
Description |
Completed |
C1. |
Copy Distribution to Mirrored Directories [3] |
_ |
C2. |
Deploy JAR to Apache Java-Repository |
_ |
C3. |
After 24 hours, update "Acquiring" page on website |
_ |
C4. |
Post an announcement to lists and website |
_ |