raboof commented on issue #388: URL: https://github.com/apache/tooling-trusted-releases/issues/388#issuecomment-3607888071
> So it's a terminology distinction: on the one hand **release candidates**, which are not approved by a PMC and not distributed to the public; and on the other hand **alpha, beta, and milestone releases**, which are approved by a PMC and distributed to the public. It's possible that different PMCs use different terminology: it's possible that one PMC makes 'alpha' packages that are only meant for use internally to contributors/developers and are not voted on (i.e. "not real Releases"), while another PMC makes 'alpha' packages that _are_ voted on and suitable for (bleeding-edge) developers outside of the project (i.e. "real Releases"). The main distinction is that if it's gone through the full release process (including vote) it's a "real Release", and if it's not, it's not. > what is the coupling of version number components to the release status grades in our release policy? Is it possible to release with "RC2" in the name despite the terminology "release candidate" being reserved in the release policy for unapproved, non-public releases? 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. -- 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]
