...
0 | Ensure that the master POM and Struts Annotations have current releases. | ||
---|---|---|---|
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, commit the POM changes, and note the revision number | ||
3 | Tag the release by making a SVN copy of the head or designated revision | ||
|
| ||
4 | Assemble the release (see notes) | ||
|
| ||
5 | Under CygWin or Linux, sign the Maven artifacts (in | ||
|
| ||
6 | Deploy the Maven artifacts to the staging repository | ||
| Make sure the staging repository at {{ http://people.apache.org/builds/struts/m2-staging-repository}} is empty or missing, then:
| ||
7 | Sign the Maven artifacts (in | ||
|
| ||
| (Under CygWin, use the | ||
8 | | ||
9 | Update your usual working copy, change the POMs to next version number, add the "-SNAPSHOT" suffix, and commit the POM changes. | ||
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 | ||
|
| ||
12 | Announce the test build to the dev list first. Wait 3-7 days and, if appropriate, post a release/quality vote. If the distribution is being mirrored (there was a favorable release vote), copy the ZIPs to |
...