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 15:32:10 UTC
[GitHub] janpio commented on issue #191: Inconsistent procedure in case of
failed release vote
janpio commented on issue #191: Inconsistent procedure in case of failed release vote
URL: https://github.com/apache/cordova-coho/issues/191#issuecomment-412560030
While having nicely incrementing release numbers, I think scrapping the release and starting over is mostly the better option. 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")
----------------------------------------------------------------
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