Struts Action 1.3.2 Release

Info

Struts Release Guidelines 2. Signing Releases
3. Apache Mirroring Guidelines

Release Manager

The release manager is Don Brown

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 Action 1.3.2 (when it is available), here are the simplest installation instructions that can possibly work:

Download the Struts 1.3.2 distribution from http://svn.apache.org/dist/struts/action/v1.3.2/ (when it is available.) (Until then, try a snapshot.)
Extract the distribution to a likely location (/opt/struts-action-1.3.2)
Install Java and set JAVA_HOME
Install Maven 2 and set MAVEN_HOME
Install Apache Tomcat
http://wiki.apache.org/struts/StrutsMaintenanceMaven
Change to the new folder (e.g., /opt/struts-action-1.3.2/src)
$ mvn
Wait about five minutes for Maven to download and build everything ** If you see any error messages, please do a quick search of the mail archives and/or post them on the Dev list, and if they appear to be newly introduced issues, a Jira tickets will need to be created so we can track and resolve the issue as quickly as possible. Oh, and THANK YOU for your help.

Outstanding Bugs

http://issues.apache.org/struts/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10121&fixfor=21699

Where To Report Bugs

Use JIRA to report issues: http://issues.apache.org/struts/browse/STR

You will have to Login before you can create a new issue.

Do not use Apache Bugzilla (it does not accept Struts bugs anyway).

TO DO

Preparation Checklist

	Description	Status
1.	Announce plan to dev@ list
2.	Review/Resolve Outstanding Bugs
3.	Update Release Notes
4.	Check Dependencies

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.1	Released	Struts Upload
Commons IO	1.1	Released	Required by Commons FileUpload
Commons Logging	1.0.4	Released	core (logging all over)
Commons Validator	1.3.0	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)	All fail
3.	Play test examples application (TC 5.0.x)

Cactus Tests

	J2SE Version	Tomcat Version	Status
1.	J2SE 1.3.1_04	Tomcat 4.1.30	N/A
2.	J2SE 1.4.2_07	Tomcat 4.1.30	N/A
3.	J2SE 1.3.1_04	Tomcat 5.0.28	N/A
4.	J2SE 1.4.2_07	Tomcat 5.0.28	N/A

Test Build Checklist (A)

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
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="95400927-4426-4c5b-a9a2-98572dd0a16a"><ac:plain-text-body><![CDATA[	B1.	Create Sums and Sign Distributions [2]	]]></ac:plain-text-body></ac:structured-macro>
B2.	Create a new JIRA version level (1.3.2)
B3.	Update "Acquiring" page on website and Test Downloads

Vote (B)