RussellSpitzer opened a new issue, #3894: URL: https://github.com/apache/parquet-java/issues/3894
### Describe the enhancement requested ### Describe the enhancement requested Currently releases use an auto-created staging repository. This is annoying because until the repository is closed, its description in Nexus says nothing about what's in it. If you've seen repositories described as "Implicitly created (auto staging)", this is what I'm talking about. It also forces the release automation to guess which repository it just deployed to. The new `prepare-rc.sh` lists the open repositories in the `org.apache.parquet` staging profile and, to avoid potential ambiguity, refuses to continue unless there's exactly one. Any other open repository in that profile blocks the release, including one from parquet-format, which publishes under the same groupId. To fix this we can use `nexus-staging-maven-plugin` to explicitly create the staging repository with a meaningful description, for example "Apache Parquet 1.19.0 RC3". This has two benefits: 1. A human doesn't need to inspect a repository to know which release it belongs to. 2. Automation doesn't need to guess which repository it made. The plugin reports the ID of the repository it creates, so the script knows exactly which one to verify, close, or clean up. -- Note this will have effects on the Manual Release Process Since `release:perform` uses the same `apache-release` profile, manual releases would also go through the plugin, and the repository would be closed by Maven rather than in the Nexus UI. We could avoid this by giving the plugin a separate profile but since I'm hoping we can deprecate the manual release we probably could just update the instructions. ### Component(s) Build ### Component(s) _No response_ -- 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]
