...
For a dry run, add '-DdryRun=true'. If you do a dry run, use 'mvn release:clean' to clean up after you have looked at the output.
When prompted for the SCM tag name, follow this pattern: STRUTS_2_3_\[PATCH_VERSION\] Wiki Markup
Note |
---|
For some reason, when using svn client 1.5, the release plugin might fail to tag the release, if it fails, run: |
...
- Update JIRA roadmap with tag/release date - release the version in JIRA
- 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
Vote on it
...
Post a release/quality vote to the dev list (and *only* the dev list). The example mail is on [Sample Announcements] page. Include the term "fast-track" in the subject, as: \ [VOTE\] Struts 2.0.9.1 quality (fast track).
Copy files
After the vote, if the distribution is being mirrored (there was a favourable release vote) copy the Sources and Binaries:
...
Remove the old files from under /www/www.apache.org/dist/struts/ to synchronize only the latest version with peers. All the files from /www/www.apache.org/dist/ are always mirrored to http://archive.apache.org/dist/struts/
Wait for rsync
...