Jeff, thanks for the summary! I will take a look at the token jira, https://issues.apache.org/ jira/browse/CASSANDRA-13348, since I was working on that recently.
--Dikang. On Sun, Mar 26, 2017 at 3:35 PM, Jeff Jirsa <jji...@gmail.com> wrote: > Email stuff: > - We've moved github pull requests notifications from dev@ to pr@ - if you > want to see when github issues are opened or updated, subscribe to the new > list (send email to pr-subscr...@cassandra.apache.org ), or check out the > archives at https://lists.apache.org/list.html?p...@cassandra.apache.org > > We have some new JIRAs from new' contributors. Would be great if someone > found the time to review and commit: > > - https://issues.apache.org/jira/browse/CASSANDRA-13358 > - https://issues.apache.org/jira/browse/CASSANDRA-13357 > - https://issues.apache.org/jira/browse/CASSANDRA-13356 > > There are also two trivial typo changes in GH PRs: > - https://github.com/apache/cassandra/pull/101 > - https://github.com/apache/cassandra/pull/102 > > These are trivial to commit, and I'll likely do it "soon", but there's an > open question about process: we've historically avoided using GH PRs, but I > think ultimately it's better if we can find a way to accept these patches, > especially with new contributors. I'm not aware of the what the standard is > for whether or not we need to make a JIRA for tracking and update CHANGES - > if any of the members of the PMC or committers feel like chiming in on > procedure here, that'd be great. In the recent past, I've made a trivial > JIRA just to follow the process, but it feels pretty silly ( GH PR #99 / > https://github.com/apache/cassandra/commit/091e5fbe418004fd04390eeeea0b1a > 3486167360 > + https://issues.apache.org/jira/browse/CASSANDRA-13349 ). > > A pretty ugly duplicate-token blocker got registered this week: committers > with free cycles may want to investigate (likely related to the new vnode > allocation code in 3.0+): > > https://issues.apache.org/jira/browse/CASSANDRA-13348 > > Here's a spattering of a few other patches (some new contributors, some > old, but only patches from non-committers) who have patch available and no > reviewer: > > - https://issues.apache.org/jira/browse/CASSANDRA-13369 - cql grammar > issue > - https://issues.apache.org/jira/browse/CASSANDRA-13374 - non-ascii dashes > in docs > - https://issues.apache.org/jira/browse/CASSANDRA-13354 - LCS estimated > tasks accuracy > - https://issues.apache.org/jira/browse/CASSANDRA-12748 - GREP_COLOR > breaks > startup > > We had 3 tickets opened to update embedded libraries to modern versions > - JNA - https://issues.apache.org/jira/browse/CASSANDRA-13300 (committed) > - Snappy - https://issues.apache.org/jira/browse/CASSANDRA-13336 (stilll > open until I check the dtests a bit more closely) > - JUnit - https://issues.apache.org/jira/browse/CASSANDRA-13360 > (committed) > > Since we had 3 of those in a short period of time, I've created an umbrella > ticket for any other libraries we want to upgrade with 4.0 - > https://issues.apache.org/jira/browse/CASSANDRA-13361 . We don't typically > upgrade libraries until we have a reasons, so if you've been unable to use > a feature of a bundled library because we were stuck on an old version, the > time to update it in trunk is now (before 4.0 ships). > > Finally, we still have a TON of open "missing unit tests" tickets - > https://issues.apache.org/jira/browse/CASSANDRA-9012 - new contributors > may > find those to be good places to have an immediate impact on the project. > > - Jeff > -- Dikang
