Hello again project! Starting with 4.1 as usual, we're closing in. We have 3 tickets open blocking beta, 1 of which is in review, that can be found here: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484
We currently need an assignee on https://issues.apache.org/jira/browse/CASSANDRA-17894, a failure in topology_test in the python dtest suite. If anyone has some spare cycles to pick this up that'd be great as we're closing in on the 4.1 release. We discussed in JIRA + ML a balanced approach to cutting 4.1 GA, which was having 1 green run to cut beta and 3 green runs in a row to cut GA (correct me if I'm wrong here Mick). To that end, checking in on 4.1 Butler we see we're at 6 failures on run 162: https://butler.cassandra.apache.org/#/ci/upstream/compare/Cassandra-4.1/cassandra-4.1. This appears to be a pretty consistent number of failures and the history in butler shows that the failures are scattershot all over the test suites; we're probably going to have to continue to whack-a-mole these flaky failures down as long as we keep "Green ASF CI" as our gatekeeping metric as this is inherent in the current runtime environment. I'll personally be taking on that subset of the Build Lead role for so long as nobody volunteers, creating JIRAs for test failures and linking them up in Butler for at least 4.1 (and any tests failing on 4.1 + other branches). In the future the link above for the kanban board for 4.1 blockers should have JIRAs for test failures post build 162 that need to be looked at. [New Contributors Getting Started] If you're looking for an easy place to get your feet wet, that test failure above could be a good starting point. Another place to check is the tickets flagged as "lhf" (low-hanging-fruit) or otherwise flagged as Starter Tickets in our kanban here: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484&quickFilter=2162&quickFilter=2160. There's a good body of work to pick from there. If you're feeling more freeform, you can search JIRA for a specific topic of interest: replace "ReplaceTextHere" with the topic on the following JIRA search: https://issues.apache.org/jira/issues/?jql=project%20%3D%20cassandra%20AND%20resolution%20!%3D%20unresolved%20AND%20assignee%20is%20EMPTY%20AND%20summary%20~%20%27ReplaceTextHere%27%20ORDER%20BY%20priority%20ASC To get situated, here's an explanation of various types of contribution: https://cassandra.apache.org/_/community.html#how-to-contribute An overview of the C* architecture: https://cassandra.apache.org/doc/latest/cassandra/architecture/overview.html And here's our getting started contributing guide: https://cassandra.apache.org/_/development/index.html We hang out in #cassandra-dev on https://the-asf.slack.com and there's a @cassandra_mentors alias you can use to reach a bunch of us that have volunteered to help newcomers get situated. [Dev list Digest] https://lists.apache.org/list?dev@cassandra.apache.org:lte=17d: Filtering to the last 17 days as we're a touch off our 2 week cadence. Blake Eggleston brought up the removal of JDK8 support from trunk in the following thread: https://lists.apache.org/thread/8cdkpj7c6po1mn140k3mlwdx73gr74wq. There appears to be a consensus around it and Ekaterina's working on JDK17 support as mentioned in a previous project update, so expect to see JDK8 dropped in 4.2/5.0. David Capwell brought up some ambiguity in our semantics w/LWT support for "UPDATE ... SET name = name + 42" when a column or row are NULL here: https://lists.apache.org/thread/jy8rodzhxz6zrb4k6trnho2w3bl3kxf1. The general consensus was to match SQL semantics. Ekaterina Dimitrova brought up the discussion for clarification around us introducing new dependencies on JDK internals as they seem to be unstable (who would have thought? ;)) here: https://lists.apache.org/thread/33dt0c3kgskrzqtp4h8y411tqv2d6qvh. Settled on update to coding style and giving a heads up on dev list and JIRA if a new dependency is added. The conversation around CEP-20 and Dynamic Data Masking continues: https://lists.apache.org/thread/68rq1og4r8t7wm8xyrfw4cbclgyczsc1. There's a directional vote around preferences to see if we have a general consensus on the right way to go with the design. So far the votes are trending towards "A) We shouldn't prefer neither approach, and I agree to the implementor selecting the table schema approach for this CEP" so if you have an opinion speak up on that thread. Last but not least we have meetups and calls for papers for October in London and Amsterdam: https://lists.apache.org/thread/64kz5qzpflzcl82y0tv7gb7pfsbhqozc. If you're in the area and interested in attending a meetup, and have something to talk about, hop to! :) [CI Trends] https://butler.cassandra.apache.org/#/ Here's our trends on our branches for the last two weeks: 3.0: 7 -> 7 3.11: 10 -> 16 4.0: 5 -> 8 4.1: 13 -> 7 trunk: 8 -? 7 Contracting on 4.1 and bouncing around a bit on 3.11. A quick spot check of the failures on build 387 on branch 3.11 (https://butler.cassandra.apache.org/#/ci/upstream/compare/Cassandra-3.11/cassandra-3.11) look environmental (timeouts and "failed to compile cassandra" errors) so I expect this to drop back down on subsequent runs. [Release progress] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484&quickFilter=2175 4.1 alpha + beta + rc: 8 issues total - Variety of test fixes - Fix in speculative execution threshold unit mismatch that would have forced all nodes on 4.1 to speculate on all queries (CASSANDRA-17877) - Fix to allow Release Version to be null in MigrationCoordinator during schema pulls as we could NPE out on edge cases (CASSANDRA-17864) - Making upsert w/adder consistent w/numbers and strings in LWT (CASSANDRA-17857) - Added plugin support for CQLSH (CASSANDRA-16456) 4.X / Next: 4 issues - Make sure preview repairs don't optimize streams unless configured to (CASSANDRA-17865) - Optionally avoid hint transfers during decommission (CASSANDRA-17808) - Disable auto snapshot on selected tables (CASSANDRA-10383) (Ticket from 2015 here!) - Add prioritization logic for CompactionTasks (CASSANDRA-17851) So close to 4.1 beta... ~Josh
