Adding a new version branch and other post-release tasks

Planning checklist

1. Make sure we have planning for at least three releases (User Stories/Technical Stories, release dates)
2. Once release and scope is determined, identify testing strategy and plan what is the anticipated testing for the release. Document this in the release planning page. 

Pre-Release Checklist

1. Make sure we have all the final common libraries(web Services, common Types) 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)
   1. Make sure that all wiki pages are restricted(viewable by CONNECT team only)
3. Create next release versions on both FHAC and CONN.

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 in both FHAC and CONN
4. Open release to the community by opening up all wiki pages for external community view.