...
0 | Ensure that the master POM and Struts Annotations have current releases, and review JIRA for any issues without a fix version set, and for any issues that should be resolved for the pending release. | ||
---|---|---|---|
| Edit the | ||
1 | Delete the struts2 items in your local Maven2 repository and obtain a fresh checkout.
| ||
2 | Update the POMs to remove "-SNAPSHOT" from the version, and update the version number in the | ||
| Update the | ||
| Commit the changes, and note the revision number. | ||
3 | Tag the release by making a SVN copy of the head or working branch | ||
|
| ||
4 | Assemble the release (see notes) | ||
|
| ||
5 | Create a release folder at people.apache.org://www/people.apache.org/builds/struts/#.#.#, and make sure the staging repository at {{ http://people.apache.org/builds/struts/m2-staging-repository![]() }} is empty or missing | ||
6 | Under CygWin or Linux, sign the Maven artifacts and deploy them to the staging repository ( | ||
|
| ||
| (Under CygWin, use the | ||
7 | Sign the Maven artifacts (in | ||
|
| ||
8 | | ||
| Afterwards, check the permissions to be sure all uploaded files a world readable and group read/writable (chmod a+r / chmod g+w) | ||
9 | Leaving the clean STRUTS_### folder be, update your usual working copy ( | ||
10 | Update JIRA roadmap with tag/release date; Add next milestone to the JIRA roadmap; Create DONE and TODO filters, share with all, and remove obsolete TODO filter; Create new release page, link from Migration Guide, and link to prior release page and JIRA filters. Update site.xml with link to new release notes. | ||
11 | Deploy the new snapshot from the Struts 2 trunk (with the latest POMs) | ||
|
| ||
12 | Post a release/quality vote to the dev list (and only the dev list). | ||
| After the vote, if the distribution is being mirrored (there was a favorable release vote), copy the ZIPs to | ||
| | ||
| Create a | ||
| Wait 24 hours before updating the | ||
| You must review the | ||
| After updating the site, be sure that the permissions are set to group writeable ( |
...
Interim Notes on Cobbling a Distribution
To update the Java 4 distribution
Before tagging
- If needed, update the translator JARs and translate batch file under "backport"
- If needed, update the translate batch file as to the Struts version under "backport"
After assembly, before signing
...
- In the Struts 2.0.x distributions, this folder was called "j4".
...
Before signing
- There's a bug in the current Maven GPG. The workaround is, before signing, under each application's target folder, copy the application's WAR as a JAR. This should go away in the next GPG release.
...