sbp commented on issue #286: URL: https://github.com/apache/tooling-trusted-releases/issues/286#issuecomment-3589954172
I've reviewed each of the current existing policy fields, and classified them into immutable (marked `[I]`), mutable (marked `[M]`), or unsure (marked `[?]`). **Compose**: Source artifact paths - **[I]** must not change during checks because otherwise check results are inconsistent Binary artifact paths - **[I]** as for source artifact paths GitHub repository name - **[?]** used for uploading, and might need to be changed if e.g. there was an error in the field; this actually applies to all three phases anyway, and should perhaps be split into a general options group GitHub compose workflow paths - **[?]** as for GitHub repository name Strict checking - **[M]** it's probably fine for the RM to change this during a release **Vote**: GitHub vote workflow paths - **[?]** as for the compose workflow paths; might be useful to change it if e.g. the workflow paths have been changed and the RM forgot that; currently unused anyway as no action is associated with voting and we do not have plans to add one Email - **[I]** would be very unusual to have to change this, and should probably be considered immutable Manual voting process - **[I]** this makes substantial changes to the voting process from the very start; it should not change during a vote Minimum voting period - **[I]** this should not be changed during a vote Pause for RM - **[?]** this field does not currently do anything; we should create an issue for adding the functionality or removing the field Release checklist - **[M]** we plan to revise this to be a URL field (#315), and in general it only provides input to the vote email template Start vote template - **[M]** this is entirely mutable always **Finish**: GitHub finish workflow paths - **[?]** again, may be useful to modify in case of changes that the RM forgot about Announce release template - **[M]** entirely mutable Preserve download files - **[M]** we can envisage an RM changing their mind on this, e.g. if trying to release and finding conflicts and then deciding that the only way to solve it is to overwrite -- 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]
