Overview

As each official CONNECT version is released, tasks must be completed to prepare CONNECT for its next cycle to ensure that the integrity of each separate, fully-tested, easily implementable CONNECT version is maintained. This is also important in case newer code contributions need to be rolled back. The following is a list of tasks that need to be completed after each release to keep each version, official or non-official, fully intact with the appropriate common types, web services, Admin GUI versions, database scripts, etc. for that particular code compilation.

Pre-Release Checklist

1. Make sure all the final common libraries (web Services, common Types) are uploaded to the maven repository (Try to automate this) 
2. Create wiki/space placeholders for next release once the Release name is identified (major vs minor)
3. CONNECT_TAG create binary for release testing

Post-Release Checklist

1. Make sure all the new Regression Suites added are moved to their respective directories (from new to Standard or Bimodal or Manual or Pass-through)
2. Make sure the released version's final branches are created (both integration and final branch).(Applicable for major and minor releases only)
3. Close release version in Jira
4. Creating ticket to update readme.md to reflect the release version

...