Skip to content

Only use dev remote for security releases

Mayra Cabrera requested to merge use-dev-for-security-releases into master

What does this MR do?

Simplifies the Release process by only using dev remote when performing a security release. Per https://gitlab.com/gitlab-org/release-tools/issues/344#note_254688678

On the other hand, given our current mirroring plan of Canonical -> push -> Security -> push -> Build, we may want to only ever use dev during a security release; when we clone, bump versions, and then push back to Build, that will break the Security -> Build mirroring until we sync Build back to Canonical during the publish process. I'm not sure pushing to Security and Build during a tagging is beneficial in this case.

Related to https://gitlab.com/gitlab-org/release-tools/issues/344

Edited by Mayra Cabrera

Merge request reports