Information
We are currently investigating an issue with the editor of some pages. Please save your work and avoid to create new pages until this banner is gone.
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.