...

• Each ACS software release has an integration branch associated for development and Phase A testing
• The branch 'integration/COMMON-YYYYXXX' is created from 'master' for these purposes .during the Release Tasks activities
• This can be easily be created through the BitBucket interface

...

• After the build has finished successfully, a test session can be issues through the Jenkins release view
• Ideally, we would expect all the tests to pass, but there are a number of them historically failing
  • In the meantime, a better approach is to compare the number of failures with previous test runs and expect a similar number

Finishing

After all the tests are passing and the pull requests date for the release in Release Calendars has been reached, Publishing the pre-release to IRM and the stakeholders is required. Once IRM has finished the verification phase, the release can be published internally and to the community according to the Release Calendars.