sbp commented on issue #388: URL: https://github.com/apache/tooling-trusted-releases/issues/388#issuecomment-3607983531
> I think the point is kind of moot: while I could go either way on whether I think the release policy forbids referring to the RC as "RC" after the vote has passed, in any case it's confusing and we shouldn't do that. Agreed. I think what I might do is add a JavaScript check to the page to start a release, on the form where you have to enter the version, and if it detects an rc-style tag in there it warns and documents why that's potentially a bad idea. Then the release manager is made explicitly aware of what they're deciding to do, and how ATR works. Alternatives considered: adding a check, and forbidding rc-style tags entirely. We can't add a check for this because checks only apply to files within a release. Those might have rc-style tags too, of course, but we actually _allow_ those tags in filenames because they can be removed before release. Also, the version cannot be changed after a release has started without deleting the whole release and starting again. We could forbid rc-style tags entirely, as I suggested above, but if the release manager is making an explicit choice even after we've documented exactly why rc-style tags should not be used for a finished release then there's probably an important reason for that and we'd at least know who the release managers are that we need to discuss this with. -- 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]
