flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Mattmann <mattm...@apache.org>
Subject Ideas for dealing with less VOTEs per RC
Date Wed, 18 Sep 2013 18:03:09 GMT
Hi Folks,

In response to your board report for September 2013, I had some
suggestions for dealing with the problem of getting less and less
VOTEs per RC you roll.

 One thing you may want to do is suggest is for the RM to ask the PMC if
VOTEs may be "carried through", especially in the case of some minor
update to a new RC that doesn't involve a critical bug fix (e.g.,
an RC only b/c of a documentation issue, etc.) Sometimes this can
solve the stagnation issue. Another idea is to think about a lazy
consensus release model, and to lower the barrier for release
vetting. E.g., see if you can define a "minimum bar" even if it's
simply verifying the sigs, and checksums and building the code for
a +1. If you can get 3 +1s that way, then if you roll releases with
bugs that may motivate folks to spend their extra time testing those
bugs in subsequent releases. Finally, improvements in CI and automated
testing may help here and also in release checking for the basics
(checksums, sigs, and building). If you can script the basics and
provide that to the PMC it may encourage more of them to vote. Just
some ideas.


View raw message