sbp commented on issue #962: URL: https://github.com/apache/tooling-trusted-releases/issues/962#issuecomment-4753086244
**Requirements**: 1. Release gains an `expedited` boolean property. Can only be set when a release is created. 2. The new `ReleaseManager` role for committers cannot be used with expedited releases, and committers cannot start an expedited release. The existing member role is unchanged. 3. Votes use `TRUSTED` mode on ATR, and happen entirely in ATR. Ballot receipts are sent to `private@<pmc>.apache.org` only. 4. Expedited vote duration is fixed at `0`, meaning any duration. 5. Votes must be resolved manually by a release manager. 6. The vote passing criteria are the same as for non-expedited releases. 7. An expedited release and all its data are confidential until the artifacts are published to public SVN. In practice, we will use the end of Finish phase as the boundary. 8. Podlings cannot make expedited releases in the initial implementation. **Decisions**: 1. The confidential audience is all PMC members plus, for non-API routes, all ASF members. 2. Confidentiality will be implemented in the GET and API wrapper gates, where possible, and by adding filters to collections. 3. The `wafc` and `warm` roles will be automatically restricted in their access constructors to `wafc` for expedited releases. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
