THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- When a serious security issue arises, we should try to create a
STRUTS_#_#_#_X
branch from the last GA release (from tag), and apply to that branch only
the security patch. - If the patch first applies to some other dependency, implore the other group to do the same, to avoid side-effects from other changes.
- Release the upcoming version in JIRA (under Administration/Manage Releases) and tag the release date
- Create DONE and TODO filters for the new version, share with all, and remove obsolete TODO filter
- 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
Obtain a fresh checkout.
Code Block |
---|
svn co https://svn.apache.org/repos/asf/struts/struts2/branches/STRUTS_#_#_#_X STRUTS_#_#_#_X
|
Change site target
Edit the top pom.xml file and replace 2.x the url below with version number that's going to be released
...