I can't believe it's been two weeks already. [New contributors getting started] As a new contributor we recommend starting in one of two places: Failing tests, or what we call "lhf" (low hanging fruit).
Query for failing tests: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496&quickFilter=2252 Query for unassigned lhf: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484&quickFilter=2162&quickFilter=2160 In Cassandra failing tests often turn out to be incredibly interesting (and tricky) to get to the bottom of. Right now we're at 18 unassigned failing test tickets. For unassigned lhf, we have 10 on 4.0.2 to pick from and 13 on 4.1.0; please feel free to ping me directly if you want some help on where to get started, or raise a flag in #cassandra-dev on slack and anyone will be happy to help out! [Dev list discussions in the past 14 days] https://lists.apache.org/list.html?dev@cassandra.apache.org:lte=14d: It's been a busy two weeks; probably why it's felt like time has flown. Ekaterina got to a good close regarding our configuration and CASSANDRA-15234, and Jacek looked to get a little clarification on what qualifies for a CEP or not with CASSANDRA-11745 (paging by bytes). In general, opening a [DISCUSS] thread here on the dev list and asking what the community thinks on CEP vs. non is a fail-safe way to get clarity if you're not sure. :) There's been a little friction around the changes to circleci config with CASSANDRA-16882; looks like maybe we closed things out and committed before we were fully at consensus on the topic. All good actors here, and this is definitely a "two way door" style change so let's keep working out the best balance and/or scripting here to support multiple workflows (run on every commit, require trigger manually, etc). CEP-17 around an SSTable format API (CASSANDRA-17056) came forth last Friday so I expect to see some interesting input on that one - if you have some thoughts here please chime in as we've something of a history of different storage engine perspectives with this project. For CEP-18, there's a pretty large ongoing discussion around modularization and whether we bundle CEP's for modularization with the artifacts that prompt their creation or keep the API changes separate. This, much like testing, maybe a little like vim vs. emacs, has been one of those topics where there's multiple schools of thought and opinion here in the project for years so working it out on a case-by-case basis is probably going to continue to be our best bet. Please chime in if you have experience in this domain (genericizing API's to support multiple implementations in mature projects, etc) and have some wisdom to offer, or an opinion on the topic in general. And last but certainly not least, after some back and forth, the vote for CEP-15 General Purpose Transactions passed! With the stipulation that the API for our distributed transactions will be modular / pluggable along with that work to allow for experimentation in the future with other algorithms. Thanks to everyone involved for working through that; I think I can safely speak for all of us when I say we're excited to see how the project evolves in this space! [Tickets in the past 14 days] On the 4.0.2 front we've closed out 9 tickets, mostly relatively modest bugfixes looks like (which is what we want to see on a .0.x line - testament to the quality of 4.0). For 4.1.0 we've closed out 13 issues; some more modest improvements and adjustments, and some nodetool options to see stored hints and consistency in output. [Tickets that need attention] No work is blocked on committers at this time. We're up from 4 to 5 tickets on 4.0.2 that are in need of reviewers - anyone with experience in any of these areas that has a few spare cycles please take a look: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484&quickFilter=2161 Up from 16 to 17 on 4.1, and there's some repeat entrants here from two weeks ago. If anyone has any ideas on the best way to link up reviewers to this outstanding work please chime in on this thread; I can say personally that rebasing something waiting for review over the CEP-10 merge was an educational experience and great way to get to know some of the code changes. ;) But in general, the faster we can go from patch available to merged the more efficient for the project in terms of rebasing costs. We have a large number of tickets that are "stalled", meaning they haven't been touched in 30 days. Please check this filter and, if any of these are assigned to you and their status doesn't reflect the current state (i.e. on backburner, back to backlog, etc), please update the tickets as needed: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484&quickFilter=2171&quickFilter=2155 It's been a fun two weeks everyone, and thanks for your professionalism and effort on some of the debates and discussions we've had. It's challenging to evolve *any* software project through major external industry evolution, and to see how vibrant and alive the Cassandra dev community remains this many years after its inception is truly remarkable. ~Josh
