# Omnibus-gitlab release process Our main goal is to make it clear which version of GitLab is in an omnibus package. ## On your development machine - Pick a tag of GitLab to package (e.g. `v6.6.0`). - Create a release branch in omnibus-gitlab (e.g. `6-6-stable`). - Change [the gitlab-rails version in omnibus-gitlab]. In our example that would be `version "v6.6.0"`. - Commit the new version to the release branch ```shell git commit -m 'Pin GitLab to v6.6.0' config/software/gitlab-rails.rb ``` - Create an annotated tag on omnibus-gitlab corresponding to the GitLab tag. GitLab tag `v6.6.0` becomes omnibus-gitlab tag `6.6.0.omnibus`. ```shell git tag -a 6.6.0.omnibus -m 'Pin GitLab to v6.6.0' ``` - Push the branch and the tag to the main repository. ```shell git push origin 6-6-stable 6.6.0.omnibus ``` ## On the build machines ### One-time - Set up the `attach.sh` script ```shell sudo su - omnibus-build cat > attach.sh <