Releases could be done by GitLab CI
I am thinking that releases should be done by GitLab CI. Here are some reasons why:
- predictable environment
- logs of the process (instead of being on the release manager's laptop)
- possibility to set ENV variables (e.g. slack URL for posting messages before, during, after the release) similar use case for omnibus-gitlab: https://gitlab.com/gitlab-org/omnibus-gitlab/issues/1184
- possibility to parallelize the EE & CE releases!
- Ensure the release-tools tests pass before doing a release
Faster, better, stronger!
A release could be triggered by pushing a tag to this repo:
-
8.6.2
would release8.6.2
version for EE & CE -
8.6.2-ce
would release8.6.2
version for CE only -
8.6.2-ee
would release8.6.2
version for EE only
The release could also be triggered by a new version in a specific file but I think the tag approach is probably better...