Hi Alex, On Mon, Dec 8, 2014 at 5:47 PM, Alex Harui <aha...@adobe.com> wrote:
> ...My takeaway is that we can vote +1 without checking everything each time... Definitely, OTOH it's good for voters to briefly indicate what they checked (signatures, build on platform X, etc.) along with their votes - also so that others can fill in the gaps if needed. This helps establish the PMC's overall confidence in how releases are actually checked. So as I said if you checked a release based on a Git tag T1 and a new release is built out of T2 you might just review the T1 -> T2 diffs, verify that the T2 archive contents match the T2 Git tag (comparing file digests with a script for example) and be happy to vote +1 on the T2 release without re-checking all the details. >...Are you opposed to having folks who voted +1 on the prior RC offer > carryover votes for those next RCs?... I'm actually recommending to drop RCs altogether, just work on individual releases that are either accepted or rejected. If one is rejected, forget it and move to the next version number. Carryover doesn't apply in this case, but people are free to use techniques like outlined above to get the confidence that they need to vote +1 on the new release. In the above example case you might vote +1 saying that you just checked the diffs with T1 that you already checked. -Bertrand
