I like the template, I would prefer a complicated vote that make people aware of all the stuff we release as PMC.
Maybe it's possible to make more a checklist for the binaries part assuming +1 is good for source and release you check. Only if -1 and binaries checked we may need to cancel. (Or not) +1 (check maven + windows installer) giving my +1 indirectly to os installer and linux installer by trusting other PMC. So maybe if we have only one PMC who check os installer is still releasable by the trust of others. Regards Eric -----Message d'origine----- De : Neil C Smith <[email protected]> Envoyé : jeudi 3 octobre 2019 19:08 À : dev <[email protected]> Objet : Re: [DISCUSS] Handling convenience binary vote(?) for 11.2 On Thu, 3 Oct 2019 at 17:00, Laszlo Kishalmi <[email protected]> wrote: > In case if we would like to vote on binaries, IMHO, I'd go with a > mixed option. We could keep the source and the binary zip distribution > on a single thread as they have "instant visibility". Then vote on the > installers (probably by platform) and other binaries on separate threads. That's a good point about per-platform installer votes. I'd been having similar thoughts, at least the whole thing that bugs me about changing what we've been doing is the added complexity while still not actually ensuring that *someone* has looked at eg. the installer for any particular platform. Assuming we don't require every voter on a release to check every binary on every platform! :-) We've never had the binary zip as part of the vote thread before, although I know some people have checked them in the vote threads I've tallied. Still, Daniel's comment "If it's not source code, you cannot reliably vote on anything." makes me want to keep the votes (if not necessarily the threads) separate. One option might be to run multiple votes in the one thread with the following template (ie. copy and paste in the reply)? Or is this too damn complicated? eg. ======================= Apache NetBeans source release Before voting +1 PMC members are required to download the signed source code package, compile it as provided, and test the resulting executable on their own platform, along with also verifying that the package meets the requirements of the ASF policy on releases. Release vote (+1 / -1) : Apache NetBeans convenience binaries Further to voting on the release, you may vote on the associated convenience binaries. As well as checking any artifact functions correctly, you should check that it has been correctly signed by a PMC member, and that the source voted on above is sufficient to build the relevant binary. Vote (+1/-1) on each, or leave blank if unchecked. Binary zip distribution and NBMs : Maven artifacts : Windows installer : macOS installer : Linux installer : ========================= So, one complicated vote thread or six simpler ones maybe? We should consider using wording similar to the above, which is mostly from the release guidelines, to clarify what needs doing anyway. Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
