raboof commented on issue #388: URL: https://github.com/apache/tooling-trusted-releases/issues/388#issuecomment-3607664774
> This may imply that TLPs have some kind of need that is not covered by the release policy, or that they are unaware of this part of the policy The distinction the release policy is making is between "real Releases" and "not real Releases": "real Releases" are things that have been properly voted on by the PMC, "not real Releases" are all other things - the "raw source repositories, nightly builds, snapshots, release candidates, or any other similar packages". As an example, Pekko is currently voting on `2.0.0-M1-RC1`, and if this vote passes, this code will be released as `2.0.0-M1`. The fact that this version ends in `-M1` does not imply that it is a "not real Release", it is the other way around: the fact that we have properly voted on it as PMC makes it a "real Release". This is in line with the release policy - it does not forbid "version numbers which appear to contain a pre-release component" - for example the last bullet in https://www.apache.org/legal/release-policy.html#release-types explicitly highlights "real Releases" that are nonetheless "milestones intended only for bleeding-edge developers working outside the project". -- 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]
