ICT ALMA Common Software

Space shortcuts

Page tree

ICT

What is an ACS Pre-Release/Release?

An ACS pre-release is a build of the integration branch of a given release with a number of 'New Feature', 'Improvement', 'Bug', etc. tickets merged into it (Last pre-release should include all the release changes). The ACS pre-release only has the developers good-to-go checks and may not include any interaction with other subsystems.

An ACS release is a build of the integration branch of a given release including all the changes planned for the release. The ACS release has the IRM team verification phase finished and all the passing tickets should be part of this release. If any of the tickets was considered a failure, then this should be removed from the release plan and not be part of the ACS release.

At the end, the ACS pre-release/release build is an artifact copied over from Jenkins to the webdav server, which can either be done manually, or using the job prepared in the release view in Jenkins.

More information of the structure of these files can be found in Release Deliverable page.

Frequency

  • ACS Pre-releases and ACS Releases are expected to be published for each ALMA COMMON release
    • The minimum number of them is one ACS pre-release at the end of the implementation phase and one ACS release at the end of the verification phase
    • Optionally, intermediate ACS pre-releases could be made at intermediate points to help developers start working with bigger changes (RTI DDS, Java 11, Python 3, etc.)
    • Additional ACS pre-releases/releases may be required if important bugs are found in one of the published versions

ICT Workers

An e-mail has to be sent to ICT-workers with similar format to:

Dear colleagues,
    at [1] you'll find our latest <pre-release/release> (<build date>):

  ExtProd-<git commit-id>-<BuildFarm Seq#>-<OS>-<ARCH>.tar.bz2
  ACS-<git commit-id>-<BuildFarm Seq#>-<OS>-<ARCH>.tar.bz2

Release notes are available in confluence [2]. If you have any problem logging in, please let us know.

If you have any doubts regarding the file names and other topics with the pre-releases and releases of ACS, please remember we prepared a confluence page in [3].


Release Notes Summary
... <List of most significant notes>

Possible Problems
... <List of known intrusive changes>

On behalf of the Common Infrastructure team,
<Name>

[1]: http://webdav.sco.alma.cl/restricted/<Releases/PreReleases>/<Release Version>/<OS>/
[2]: https://confluence.alma.cl/display/ICTACS/<Release Version>
[3]: https://confluence.alma.cl/display/ICTACS/Release+Deliverable

ACS Community

For the community, only the final release is notified and made available through the public repository.

Repository

Once the verification phase of the release has been finished by the ICTIRM team, and the pull requests have been merged back to the master branch of the internal ACS repository, the following tasks have to be performed:

  • Create branch acs/YYYYMMM
  • Run scripts for migrating acs/YYYYMMM branch to the public repository

Publish

For the community an e-mail to the ACS Discuss list has to be sent with similar format to:

Dear ACS community,
    we have added the <Release Version> release to the public repository [1].

Release notes are available in confluence [2]. If you have any problem logging in, please let us know.


Release Notes Summary
... <List of most significant notes>

Possible Problems
... <List of known intrusive changes>

On behalf of ALMA's Common Infrastructure team,
<Name>

[1]: https://bitbucket.alma.cl/scm/asw/acs.git
[2]: https://confluence.alma.cl/display/ICTACS/<Release Version>
  • No labels