Page History

...

1. When a serious security issue arises, we should try to create a STRUTS_#_#_#_X branch from the last GA release (from tag), and apply .

   Code Block
   svn copy https://svn.apache.org/repos/asf/struts/struts2/tags/STRUTS_#_#_# https://svn.apache.org/repos/asf/struts/struts2/branches/STRUTS_#_#_#_X -m "Creating new branch"

2. Apply to that branch only
   the security patch.
3. If the patch first applies to some other dependency, implore the other group to do the same, to avoid side-effects from other changes.
4. Release the upcoming version in JIRA (under Administration/Manage Releases) and tag the release date
5. Create DONE and TODO filters for the new version, share with all, and remove obsolete TODO filter
6. 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, secure the page to allow access only member of struts-committers group in Confluence

...