Hi folks, I wonder if we can change the release process in the following way:
For each Vote candidate: Synchronization of all bits (of course sources are mandatory) maven artefacts, installers (certified) -- A vote with everything inside with asking after normal check (licence+checksum) for example which installer on which os. If source is wrong because of license, vote will be cancelled so we have to regenerate everything. Was done for 11.3 not a big deal just time until we got a fix. If everything in source is ok, then will go for normal tally with one PMC vote per installer minimum. If I analyze on 11.3 it's only +1 or +0. So if 11.3 vc1 license has been ok we would have save 72h. We lost a certification per non valid voting candidate (not sure how much it cost) If tally conduct to a release with an installer weird, if tally cover, just release. And fix only the wrong installer. Best Regards Eric --------------------------------------------------------------------- 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
