Creating Releases

Repo Summary

There are three repositories at present for Acquia CMS.

acquia/acquia_cms - this repository, from which development happens and all releases are started.
acquia/acquia-cms-project - the public facing repository (eventually), from which customers will run composer create-project and our UIs will pull deploy artifacts.
acquia/sf-acms - a Site Factory specific repository that builds and stores its' own version of ACMS releases, customized to run inside ACSF.

Developers checkout a feature branch on their local machines, commit code
Developers push the feature branch to the repository, open a PR against the 'develop' branch.
Tests run, and if passing and all peer-review feedback has been implemented, a technical lead will merge the PR.
This will deploy the merged commits to our ACE integration environment, and kick off a build to on acquia/sf-acms to deploy the commits to our ACSF integration environment.

A technical lead will create a release branch off of develop, and cut a tag against HEAD on that branch and push it to the main repo.
The technical lead will then deploy the new tag to the Stage environment in our ACE and ACSF integration environments, where UAT will take place.
Once UAT is completed, a PR will be issued to merge the release branch (and its' tag) into the 'main' branch. HEAD on 'main' should always represent the most recent known deployable state at any given point in time.
This merge PR will generate a similar tagged release build in the 'acquia/sf-acms' repository.
The technical lead will then deploy the tagged release to Production in both our ACE and ACSF integration environments.
Product and the technical lead will work together to create release communications (process TBD)

acquia/acquia-cms-project and configures its composer.json file to pull in any tagged releases with a simple composer update.