...
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. | ||||
---|---|---|---|---|---|
| Create an "omnibus" ticket in JIRA to refer to in upcoming release related commit comments and for general documentation purposes. Mark it with priority "Blocker". | ||||
| Edit the | ||||
1 | Delete the struts2 items in your local Maven2 repository and obtain a fresh checkout. For a trunk release, that is
Alternatively, for a 2.0.x branch release:
| ||||
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 ( | ||||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="fa7d0203710a6d0b-52bd9ed4-4944494a-8febb22e-57b37153959e85822dd64d45"><ac:plain-text-body><![CDATA[ | 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 Notes X.X.X] release page, link from [Migration Guide], and link to prior release page and JIRA filters. Update site.xml with link to new release notes. | ]]></ac:plain-text-body></ac:structured-macro> | ||
11 | Deploy the new snapshot from the Struts 2 trunk (with the latest POMs) | ||||
|
| ||||
| At this point the omnibus ticket can safely be set to resolved. | ||||
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 ( |
...
1 | Install cgywin, including utils/gpg |
---|---|
2 | Generate a key with |
3 | Backup your cygwin home directory to another media |
4 | Add Append your key to {{ https://svn.apache.org/repos/asf/struts/maven/trunk/build/KEYS![]() }} and commit the change (see the KEYS file for instructions). After committing refresh the KEYS file at |
5 | Add this key to a public keyserver (such as pgpkeys.mit.edu) |
Update Maven settings for our servers
...