+1
On Tue, Feb 8, 2022 at 3:37 PM Joshua McKenzie <jmcken...@apache.org> wrote: > I find myself agreeing with Jeremiah's sentiment here. > > For example, we're asking people that are on 4.0.1 to make the difficult > choice between accepting the risk of whatever prompts an urgent release vs. > accepting the risk of potentially destabilizing their GA critical > infrastructure. The 4.0 line is regressing, at least from a CI perspective: > https://butler.cassandra.apache.org/#/ci/upstream/trend > > I'm a -0 on this release as structured; given we discussed this exact > situation when we adopted the new procedures I personally accept us moving > forward right now and wouldn't block the release, but going forward I'd > like to see us cut hotfix releases based on the latest GA plus a minimal > patchset to address whatever urgent need a release is targeting so long as > CI is in a regressing state. > > > On Tue, Feb 8, 2022 at 3:18 PM Jeremiah D Jordan < > jeremiah.jor...@gmail.com> wrote: > >> -1 nb >> >> So we just voted on an approved the CI process page recently: >> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=199530280 >> >> Where we said: >> "All releases by default are expected to have a green test run on >> ci-cassandra.apache.org Jenkins. In exceptional circumstances (security >> incidents, data loss, etc requiring hotfix), members with binding votes >> on a release may choose to approve a release with known failing tests.” >> >> I do not see green CI runs recently for 4.0. >> https://ci-cassandra.apache.org/job/Cassandra-4.0/ >> >> If we are making this release for a security incident/data loss/hot fix >> reason, then I would expect to see the related change set only containing >> those patches. But the change set in the tag here the latest 4.0-dev >> commits. >> >> Do we want to be violating our goal of only releasing with green CI less >> than a month after the vote? >> >> -Jeremiah Jordan >> >> On Feb 7, 2022, at 8:14 AM, Mick Semb Wever <m...@apache.org> wrote: >> >> Proposing the test build of Cassandra 4.0.2 for release. >> >> sha1: 25012d2fec1984cc9c1a352f214eb912ca4f10f5 >> >> Git: >> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.2-tentative >> >> Maven Artifacts: >> https://repository.apache.org/content/repositories/orgapachecassandra-1255/org/apache/cassandra/cassandra-all/4.0.2/ >> >> The Source and Build Artifacts, and the Debian and RPM packages and >> repositories, are available here: >> https://dist.apache.org/repos/dist/dev/cassandra/4.0.2/ >> >> The vote will be open for 72 hours (longer if needed). Everyone who has >> tested the build is invited to vote. Votes by PMC members are considered >> binding. A vote passes if there are at least three binding +1s and no -1's. >> >> [1]: CHANGES.txt: >> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0.2-tentative >> [2]: NEWS.txt: >> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0.2-tentative >> >> >>
