On Thu, 9 Jan 2025 at 11:09, Piotr P. Karwasz <pi...@mailing.copernik.eu> wrote: > First of all, I share your intention of having the largest number of > users test our Release Candidates before the official release. If other > projects were able to test our candidates **before** the end of the > voting period:
In NetBeans we use different terminology here, which reflects a slightly different approach. We have release candidates for user testing, and voting candidates for release voting. We expect functionality testing to happen **before** the **start** of the voting process. Our voting candidate is always built off of the same git hash as the final release candidate. The vote is for the PMC and community to verify everything. Needing to pull the vote happens only occasionally, and we go back to another release candidate phase before progressing to another voting candidate. At the moment we're using nightlies.apache.org for the RCs, and they are not voted on / official releases (and that is made clear). We're not publishing RCs of the many Maven artefacts that make up the platform. Given a recently reported issue, that might be something we need to consider. OTOH, there are rather a lot of them. But if we need to do that, I don't see a huge problem in voting to do so. IIRC the 72hrs voting period is also marked "should" not "must", and perhaps publishing RCs is something PMCs could agree to have curtailed votes on, while still enforcing the "act of the foundation" bit? 2c, best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
