Page Comparison

||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|          |          |kaspermarkus|Release Manager [creates the tarballs\|Creating the Tarballs - Detailed Description]|
|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 tarballs ([desc. here\|http://wiki.collectionspace.org/display/collectionspace/Process+for+QA+and+Releasing#ProcessforQAandReleasing-Creatingthetarball])manual installation instructions and modifies the install instructions 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|