Inconsistent procedure in case of failed release vote

[brodycj]

In case of a failed release vote the procedure for tools is to continue with the next release tag while the procedure for plugins and platforms is to reuse the same tag with help from git tag --force. I really do not favor the use of forced tag updates on GitHub.

I can think of the following alternative solutions:

1. Update the procedure for plugins & platforms to also continue with the next release tag in case of a failed vote
2. Update the procedure for tools to reuse the same tag in case of a failed vote, and update the procedure to use special "proposed" tag values to tag proposed releases for voting

[janpio]

While having nicely incrementing release numbers, I think scrapping the release and starting over is mostly the better option (so I prefer 1.).
Unless there are no real code changes - but then it doesn't make sense that the release vote fails, right?
But maybe there is an Apache rule for this as the base of this "policy"?

(As this is a "how do we do things" question, it should be posed in the mailing list - even if just with a "there is the issue, comments over there please")

[brodycj]

I will check this when I get a chance thanks