> No release can be cut without a fully green CI run on ci-cassandra.apache.org
I appreciate the goal but this seems problematic given all four release branches (2.2, 3.0, 3.11, 4.0) + trunk appear to have about 15-20 failures on ci-cassandra.apache.org at the time of this vote. If this vote passes would that mean we cannot cut any release or does it just mean that PMCs could -1 with this as a reason? Perhaps it is possible to try to obtain a high quality bar in normal times while leaving us some wiggle room for critical bug fix releases (e.g. security patches) or other extenuating circumstances like "Releases SHOULD have a fully green CI run but MAY proceed with failing tests if those tests have a Jira issue tracking their resolution" to leave the PMC room for allowing votes with flakey/failing tests in an emergency situation? Then all we'd have to do to get out of a sticky situation is cut jira tickets ... Or if this is just a "valid reason" that a PMC could be -1 then that's fine too. -Joey On Mon, Jan 10, 2022 at 11:00 AM Joshua McKenzie <jmcken...@apache.org> wrote: > > Wiki draft article here: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=199530280 > > The vote will be open for 72 hours (it's short + early indication on > discussion was consensus). > Committer / pmc votes binding. > Simple majority passes. > > References: > Background: original ML thread here: > https://lists.apache.org/thread/bq470ml17g106pwxpvwgws2stxc6d7b9 > Project governance guidelines here: > https://cwiki.apache.org/confluence/display/CASSANDRA/Cassandra+Project+Governance > > ~Josh
