Page History

...

Initial rename of packages and configuration files	Complete
Pass Web``Work2 codebase through the Incubator	Complete
Setup Nightly Builds	Pending
Update WW2 documentation for Struts 2	Complete
Utilize Cookbook format for Showcase and add Struts-Examples use cases
Remove deprecated members (IoC components)	Complete
Deprecate selected legacy API members (e.g. Around``Interceptor, "do" clause)	Complete
Update Javadoc to match new package and configuration naming	Complete
Implement selected new features and Struts 1 features (infra)	Complete
Add Struts 1 and WW2 Migration Guides	Initial draft added
Develop routine for exporting wiki to HTML/PDF	Complete
Develop Maven assembly to create distribution	Complete
Second documentation review	Complete
Complete standard release plan	Pending	Complete
Struts 2.0.0 is intended as a "development" distribution only

Documentation Status

...

Additional Background

• Apache Struts Release Guidelines
• Signing Releases
• Apache Mirroring Guidelines

Release Manager

The release manager is Ted Husted.

See Also

• Struts 2.0.0 omnibus ticket
• Issue Tracker
• Struts Ti Proposal
• Migration Issues
• Struts 2 Rough Spots
• Public API Whiteboard
• Retroweaver

Release Manager

The release manager is Ted Husted.

• See also Creating and Signing a Distribution

Special Issues

Struts 2.0 is based on the WebWork 2 codebase. Essentially, Struts 2.0 will be the technical equivalent of WebWork 2.3. (The WebWork 2 codebase was accepted into the Struts project through the Apache Incubator.)

...

TODO: A Silenium test suite for the applications would be great!

Test Build Distribution Checklist (A)

See also Commons Step-by-Step Guide Creating and Signing Releases

{{$ svn copy -r 447072

https://svn.apache.org/repos/asf/struts/struts2/trunk^{Image Removed} https://svn.apache.org/repos/asf/struts/struts2/tags/STRUTS_2_0_0^{Image Removed}

-m Tag r447072 as Struts 2.0.0}}

#	Description	Completed
A1.	Setup new JIRA version level or update release on Roadmap	Done
A2.	Tag release in svn: ${STRUTS_2_0_0}	Done (r447072)
A3.	Update POM version level and run Distribution Target	Done
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="5dc49866-b0eb-45f8-87cf-c935134c1f5c"><ac:plain-text-body><![CDATA[	A4.	Create Sums and Sign Distributions [2]	${STATUS}	]]></ac:plain-text-body></ac:structured-macro>		Done
A5.	Upload Distribution to people.apache.org/builds/struts/2.0.0/	Done
A6.	Deploy JAR to Apache Java-Repository	Done ${STATUS}
	$ mvn deploy -P pre-assembly
A7.	Post release-quality vote on dev@ lists	${STATUS}

...

• If release vote fails, including for a lack of quorum (3 binding +1s), remove from builds folder.
• If a release vote passes (Alpha, Beta or GA), the release may be announced and mirrored, at the PMC's discretion.
• If vote is GA, goto Checklist (C).

Point Release Distribution Checklist (B)

...

If initial vote is Alpha or Beta, voting can continue until a GA or "withdraw" vote passes, or there is a subsequent release.

General Availability Distribution Checklist (C)