sbp commented on issue #388: URL: https://github.com/apache/tooling-trusted-releases/issues/388#issuecomment-3607716106
Ah, thanks for clarifying. 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. But that doesn't explain why there are `(?i)rc[0-9]+` releases such as Apache Lucene.NET 3.0.3-RC2: https://dist.apache.org/repos/dist/release/lucenenet/3.0.3-RC2/ Perhaps these are considered alpha releases? In other words, 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? -- 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]
