This thread on dev@cordova.apache.org led to a discussion with @erisu about the number of extra commits that would persist in master in case of a failed release.
A simple solution could be to use a special tag format such as create/7.0.1 or create/2020.03.27/7.0.1 that we would use to build the npm package, and then just push the package build tag to GitHub. Then we should be able to abandon or delete it if we find a problem during the vote. I am thinking that a lot of the needed git and GitHub functionality should work with this build tag idea.
It would also be possible to make a PR or draft PR when making a release, which could be closed and abandoned if needed.
This thread on dev@cordova.apache.org led to a discussion with @erisu about the number of extra commits that would persist in master in case of a failed release.
A simple solution could be to use a special tag format such as
create/7.0.1orcreate/2020.03.27/7.0.1that we would use to build the npm package, and then just push the package build tag to GitHub. Then we should be able to abandon or delete it if we find a problem during the vote. I am thinking that a lot of the needed git and GitHub functionality should work with this build tag idea.It would also be possible to make a PR or draft PR when making a release, which could be closed and abandoned if needed.