DISCUSS thread: https://lists.apache.org/thread/o166v7nr9lxnzdy5511tv40rr9t6zbrw
Revise Release Lifecycle cwiki page (https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Lifecycle): - Ensure we have parity on jobs run and coverage between circle and asf-ci - Allow usage of circleci as gatekeeper for releases. A release will require 1 green run for beta, 3 green runs consecutively for ga - No new consistent regressions on CI for asf compared to prior branches - Explicitly do not consider ci-cassandra asf flaky tests as release blockers Changes to codify into documentation (https://cassandra.apache.org/_/development/how_to_commit.html): - On patch before commit, multiplex @500 all new tests, changed tests, or expected to be impacted tests ("expected to be impacted" piece pending multi-class multiplexing support). - Add support for / documentation for multi-class specification in multiplexer and document Add informal project commitment during next major release lifecycle to continue working on bringing asf ci-cassandra up to where it can be formal gatekeeper for release. ----------------------------------------------------------- The vote for these revisions will run through EoD 10/12/22 to give us the weekend + 72 business hours.
