Hi Justin, The staging repo in repository.apache.org is not a release.
It's content is not available in maven central or the default apache repo. The only way you can access the artifacts, is by explicitly adding the staffing repo to your project. As soon as the vote passes, you select the repo and click on the release button. Only then are the artifacts copied to Apache's main repo and synced to maven central. If the vote doesn't pass, you select it and click drop and the repo with all of it's content is simply deleted not leaving a trace. So I still don't see any issues in the way the releases are done. I would also consider the issue with the version a minor issue, but that's generally up to the ppmc to decide. And I do agree, that the number of votes doesn't match the general code activity the project usually has. Voting and doing it correctly is THE major thing podlings are supposed to learn before graduation. Chris Holen Sie sich Outlook für Android<https://aka.ms/ghei36> ________________________________ From: Justin Mclean <[email protected]> Sent: Sunday, September 29, 2019 2:59:10 PM To: [email protected] <[email protected]> Subject: Re: Release of 0.8.1 Hi, > Now as Chris and Jialin pointed out some issues, I need to release RC2. I’ve not voted on the release yet and was waiting on other PPMC members to do so. The PPMC need to be involved here not just the mentors, why haven’t any other PPMC members voted? A reminder that a -1 vote is not a veto. While I’ve not looked in detail at the issues, they seem relatively minor to me. You’re not a top level project so it’s expected there may be a few issues, and if they are minor they can be fixed in the next release. > My new question is, what should I do on repository.apache.org? Again, my advice is not to make a maven release until after the source release vote has passed. Chris may have other advice re this, but I’d try to make the release process as simple as you can. Maven is not where official release go. Thanks, Justin
