svn commit: r929961 [1/2] - in /websites/production/struts/content: development/2.x/docs/ release/2.3.x/docs/
Author: lukaszlenart Date: Fri Nov 21 09:30:05 2014 New Revision: 929961 Log: Updates production Added: websites/production/struts/content/development/2.x/docs/version-notes-2320.html websites/production/struts/content/release/2.3.x/docs/version-notes-2320.html Modified: websites/production/struts/content/development/2.x/docs/building-struts-2-normal-release.html websites/production/struts/content/development/2.x/docs/migration-guide.html websites/production/struts/content/release/2.3.x/docs/building-struts-2-normal-release.html websites/production/struts/content/release/2.3.x/docs/migration-guide.html Modified: websites/production/struts/content/development/2.x/docs/building-struts-2-normal-release.html == --- websites/production/struts/content/development/2.x/docs/building-struts-2-normal-release.html (original) +++ websites/production/struts/content/development/2.x/docs/building-struts-2-normal-release.html Fri Nov 21 09:30:05 2014 @@ -139,11 +139,11 @@ under the License. Content/**/ +/*]]>*/ 1 Getting ready2 Update Draft Docs when needed3 Be sure your local copy is up-to-date4 Create a release branch5 Prepare release6 Perform the release7 Move the assemblies8 Announce availability9 Clean up repository10 Vote on it11 Copy files12 Promote release13 Clean up old releases14 Wait for rsync15 Update site16 Redeploy the draft docs (Optional)17 Post announcements Building Steps (Struts)Getting readyCreate 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".Switch to branch developEnsure that the master POM and Struts Annotations have current releasesReview JIRA for any issues without a fix version set, and for any issues that should be resolved for the pending release.Ensure that there are no repositories or pluginRepositories listed in the poms.If you have committed all changes regarding the release process, close the omnibus ticket as it is the last open ticket for the upcoming releaseRelease the upcoming version in JIRA (under Administration/Manage Releases) and tag the release dateAdd next milestone ve rsion to the JIRA roadmapCreate DONE and TODO filters for the new version, share with all, and remove obsolete TODO filterCreate 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 releaseExport wiki pages and put them under /docsUpdate Draft Docs when neededCheckout struts-site project (see details at the bottom of this page) and perform export: Move the assembliesTo simplify testing, the assemblies have to be moved to the
/www/people.apache.org/builds/struts/$VERSIONdir.After closing repository in Nexus, check if the release files are available from staging repository as bellow: