Page History

...

1. 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".
2. Switch to branch develop
3. Ensure that the master POM and Struts Annotations have current releases
4. Review JIRA for any issues without a fix version set, and for any issues that should be resolved for the pending release.
5. Ensure that there are no repositories or pluginRepositories listed in the poms.
6. 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
7. Release the upcoming version in JIRA (under Administration/Manage Releases) and tag the release date
8. Add next milestone version to the JIRA roadmap
9. Create DONE and TODO filters for the new version, share with all, and remove obsolete TODO filter
10. Create a 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
11. Export wiki pages and put them under /docs
12. Create a new branch using git flow (or just git) - git flow release start X.X.X.X - where X.X.X.X is the version you want to release

Be sure your local copy is up-to-date

...

Code Block
git checkout develop git pull git fetch origin --prune

Create a release branch

git flow release start X.X.X.X

Now you should be on release/X.X.X.X branch (git status supposes confirm that)

Update version of archetypes

...