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. Ensure that the master POM and Struts Annotations have current releases
3. Review JIRA for any issues without a fix version set, and for any issues that should be resolved for the pending release.
4. Ensure that there are no repositories or pluginRepositories listed in the poms.
5. 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
6. Release the upcoming version in JIRA (under Administration/Manage Releases) and tag the release date
7. Add next milestone version to the JIRA roadmap
8. Create DONE and TODO filters for the new version, share with all, and remove obsolete TODO filter
9. Create new release Version Notes page in Confluence, link from Migration Guide, and link to prior release page and JIRA DONE filters of the version to release

...

ssh people.apache.org
cd /www/people.apache.org/builds/struts/$VERSION
cp struts-$VERSION-src.*  /www/www.apache.org/dist/struts/source
cp struts-$VERSION-docs.*  /www/www.apache.org/dist/struts/documentation
cp struts-$VERSION-lib.* /www/www.apache.org/dist/struts/library
cp struts-$VERSION-apps.* /www/www.apache.org/dist/struts/examples
cp struts-$VERSION-all.* /www/www.apache.org/dist/struts/binaries   

If a new DTD was defined, copy it to /www/struts.apache.org/dtds/ and change permission to struts group (chwon :struts *.dtd) and write rights (chmod g+w *.dtd).

...