The /wiki/spaces/collectionspace/pages/666275203 describes how the team scopes, designs, develops, and QAs a release.
This is a checklist of activities that wrap up a Release Cycle.
||Completed||Priority||Locked||CreatedDate||CompletedDate||Assignee||Name|| |F|M|F|1328044941200| |jesse|Tech Lead ensures no open (or reopened, or in progress) issues are still assigned to the given release.| |F|M|F|1328044997795| |jesse|Release Manager review all VMs in use and retire any that are not essential for development and/or outreach.| |F|M|F| | |heather hart|Release Manager copies forward the previous release's Documentation in the wiki for this release| |F|M|F| | |kaspermarkus|Release Manager QAs the manual installation instructions and modifies if necessary| |F|M|F| | | |When the release is available, email the Talk list that the release is available for download and include the link to the install instructions| |F|M|F| | |heather hart|If the release did not stick to the schedule, update the Road Map and release dates associated with each release in JIRA| |F|M|F| | |heather hart|Update release page with Schema changes| |F|M|F| | |heather hart|Update release page with any system requirements changes, including tools (e.g. Ant, Maven ...) version requirement changes| |F|M|F| | |heather hart|Update release page with link to JIRA issues completed during that release (example for v2.0: http://issues.collectionspace.org/secure/ReleaseNote.jspa?projectId=10000&version=10120)| |F|M|F| | |heather hart|Mark the release as 'released' in JIRA| |
||Completed||Priority||Locked||CreatedDate||CompletedDate||Assignee||Name|| |T|M|F|1437769404929|1469230487744|remillet|Release Manager creates release branches| |T|M|F|1437769427016|1469230488932|remillet|Release Manager updates demo to use release branches| |F|M|F|1328045095342| |jesse|Tech Lead ensures no open (or reopened, or in progress) issues are still assigned to the given release.| |T|M|F|1328045058129|1469230504424|remillet|Release Manager review all VMs in use and retire any that are not essential for development and/or outreach.| |F|M|F| | |mforbes@movingimage.us|Release Manager copies forward the previous release's Documentation in the wiki for this release| |F|M|F| | |mforbes@movingimage.us|Outreach manager writes a release announcement| |F|M|F| | |mforbes@movingimage.us|Outreach manager posts summary of work on collectionspace.org as news post and on wiki release page.| |F|M|F| | |mforbes@movingimage.us|Outreach Manager - Email to Talk with the link to download and post on Twitter| |F|M|F| | | |Release manager updates Current Release info on collectionspace.org| |F|M|F| | |kaspermarkus|Release Manager - Update [Current and Past Releases]| |F|M|F| | |heather hart|Outreach manager Update release page with Schema changes| |F|M|F| | |heather hart|Release manager updates release page with any system requirements changes, including tools (e.g. Ant, Maven ...) version requirement changes| |F|M|F|1437769539699| |chadnelson|Release manager updates release page with steps required to upgrade to new version| |F|M|F| | |heather hart|Release Manager updates release page with link to JIRA issues completed during that release (example for v2.0: http://issues.collectionspace.org/secure/ReleaseNote.jspa?projectId=10000&version=10120)| |F|M|F| | | |Release manager marks the release as 'released' in JIRA| |