...
Initial rename of packages and configuration files | Complete |
| |
---|---|---|---|
Pass Web``Work2 codebase through the Incubator | Complete |
| |
Pending |
| ||
Complete |
| ||
Utilize Cookbook format for Showcase and add Struts-Examples use cases |
|
| |
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 |
| |
Initial draft added |
| ||
Complete |
| ||
Complete |
| ||
Second documentation review | Complete |
| |
Complete standard release plan | Pending | Complete |
|
Struts 2.0.0 is intended as a "development" distribution only |
|
|
Documentation Status
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 | Complete |
|
Step 4 - Complete tutorials and other "TODO" sections | Complete |
|
Resources
- Apache Struts Release Guidelines
- Struts Maintenance Guide for Maven
- Signing Releases
- Wendy's notes on Release Signing
- Apache Mirroring Guidelines
Release Manager
The release manager is Ted Husted.
See Also
Additional Background
- 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
# | 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 | |||
A4. | Create Sums and Sign Distributions (see Resources) | ${STATUS} | |||
| |
| |||
|
|
| |||
Done | |||||
A5. | Upload Distribution to | Done | |||
A6. | Deploy JAR to Apache Java-Repository | ${STATUS} Done | |||
| |
| |||
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)
B1. | Update "AcquiringDownooads" page on website and Test Downloads | ${STATUS} |
---|
...
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 Distribution Checklist (C)
Description | Completed | |||
---|---|---|---|---|
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="a7cd4924-3672-4740-bebf-c712c54f8bb2"><ac:plain-text-body><![CDATA[ | C1. | Copy Distribution to Mirrored Directories [3] | ${STATUS} | ]]></ac:plain-text-body></ac:structured-macro>|
C2. | After 24 hours, update "AcquiringDownloads" page on website | ${STATUS} | ||
C3. | Post an announcement to lists and website | ${STATUS} |