Only use dev remote for security releases
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 usedev
during a security release; when we clone, bump versions, and then push back to Build, that will break theSecurity -> Build
mirroring until we sync Build back to Canonical during thepublish
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