Versions Compared

Old Version 20

changes.mady.by.user Maurizio Cucchiara

Saved on

compared with

New Version 21

changes.mady.by.user Maurizio Cucchiara

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. When a serious security issue arises, we should try to create a STRUTS_#_#_#_X branch from the last GA release (from tag). code
    No Format
    
mvn release:branch -DbranchName=STRUTS_#_#_#_X
    Read the maven release:branch docs for further details

or alternatively

No Format

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"
Note

The svn copy just copies the struts branch from the struts tags, no info about the version will be changed.

  1. Apply to that branch only the security patch
  2. Commit the fix. No reference should be make to the commit being related to a security vulnerability.
  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

...