-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document how hotfix releases differ from normal releases #202
Comments
In theory, I believe only security fixes are supposed to be allowed to have expedited releases, but the Apache guidelines aren't super explicit about this. For the record, the voting guidelines also say votes should run for at least 72 hours. (Although the release process document emphasizes "should" rather than "must"). All releases must have a minimum of three +1 votes, and there's some requirements as to what the PMC members must do before voting. |
To clarify, I'm not personally opposed to expediting an urgent bugfix release like this one. It makes sense, and it's the right thing to do. I'm just concerned that we could run into issues with the board for failure to adhere to guidelines (which has happened in the past) |
All I wrote here is of course a restriction/change to what is already documented in https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md and https://github.com/apache/cordova-coho/blob/master/docs/tools-release-process.md (which needs to be extracted into its own file as well probably). We should definitely check with Apache guidelines and whoever decides there what is possible and what is not. We just made a judgement call right now, and I wanted to start the formalisation process of that because I couldn't find anything in Cordova land. |
Suggestion:
The text was updated successfully, but these errors were encountered: