sbp commented on issue #286: URL: https://github.com/apache/tooling-trusted-releases/issues/286#issuecomment-3590134649
Since the GitHub repository name field applies to all phases, we'd have to record it for any voting actions that come from GitHub Actions too. I still think this is `[R]`, but `[R]` is more like "record action as snapshot" because it can apply to more than just revisions, potentially. Also the minimum voting period isn't the actual chosen voting period, which is always set by the RM when they start the vote. We actually don't need to know what the minimum voting period policy is for attestations, I think. Therefore I think that one is actually mutable, `[-]`. I think that strict checking is an odd one, because it's definitely something we want to keep mutable, but actually we probably do want to know what it was set to when going to the next phase. Maybe we should count this as a voting option? Then it would be `[P]`, but otherwise we'd have to make it a new sort of `[R]`. I'd really like to simplify all of this somehow. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
