hboutemy commented on issue #926: URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4249994734
> I would prefer to iterate on a pre-release. This is what we do by doing releases on Maven Central like `1.0.0-beta-1`, this is usual for 20 years: 1. pre-release = SNAPSHOT: people who do pre-release tests even for that beta, like Slawek, build (`mvn install` precisely) locally the SNAPSHOT to be able to use it for tests = what we'll do with the few Maven devs who used ATR for a few releases, doing composition file upload with ATR UI. 2. beta release (using ATR beta URL `https://release-test.apache.org/`): The beta release will be done in a next step, once the few very early "self install" testers are confident, that we'll do a public release (even beta) that can be integrated for public consumption, probably integrated as an option in [ASF parent POM that currently provides `apache-release` profile](https://maven.apache.org/pom/asf/) 3. release (using ATR GA URL when it is available): I expect to be able to do a final release when ATR GA public url becomes final. This plugin will always remain small, it's just to upload for release composition preparation during the build phase with `mvn`, it will never grow very big: wider automation is what you do with GHA ATR actions. Steps 1 & 2 will have given us the expected confidence by ATR GA. this 3 stages plan is what implicitely any Maven user would expect. -- 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]
