You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cordova.apache.org by GitBox <gi...@apache.org> on 2018/08/13 13:55:27 UTC

[GitHub] brodybits opened a new issue #191: Inconsistent procedure in case of failed release vote

brodybits opened a new issue #191: Inconsistent procedure in case of failed release vote
URL: https://github.com/apache/cordova-coho/issues/191
 
 
   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:
   - Update the procedure for plugins & platforms to also continue with the next release tag in case of a failed vote
   - 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

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org