THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Create an "Struts 2.x.y omnibus ticket" ticket in JIRA to refer to in upcoming release related commit comments and for general documentation purposes. Mark it with priority "Blocker".
- Ensure that the master POM and Struts Annotations have current releases
- Review JIRA for any issues without a fix version set, and for any issues that should be resolved for the pending release.
- Ensure that there are no repositories or pluginRepositories listed in the poms.
- If you have committed all changes regarding the release process, close the omnibus ticket as it is the last open ticket for the upcoming release
- Release the upcoming version in JIRA (under Administration/Manage Releases) and tag the release date
- Add next milestone version to the JIRA roadmap
- Create DONE and TODO filters for the new version, share with all, and remove obsolete TODO filter
- Create new Version Notes page in Confluence, link from Migration Guide, and link to prior release page and JIRA DONE filters of the version to release
| Note |
|---|
Before starting release process make sure that the Docs were exported to https://cwiki.apache.org/WW/! |
Obtain a fresh checkout.
| Code Block |
|---|
svn co https://svn.apache.org/repos/asf/struts/struts2/trunk STRUTS_#_#_# |
...