2/10/2020: Today's 4.0 status update:

The 4.0 board can be found at
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355.

The broad view: We have a total of 95 tickets open for 4.0 releases (No
change from 11 days ago, though 5 are cwiki migration tests):
https://issues.apache.org/jira/issues/?filter=12347896

Cumulative flow updated, now restricted to last 3 months:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&projectKey=CASSANDRA&view=reporting&chart=cumulativeFlowDiagram&swimlane=939&swimlane=936&swimlane=931&column=1505&column=1506&column=1514&column=1509&column=1512&column=1507&days=90

What pops for me: velocity on closes look healthy, we just had new tickets
open to match what we closed out:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1670

5 of those are the test epic + 4 test tracking tickets from me looking into
migrating cwiki stuff to JIRA.

That filter above is last 7d and it's been 11 since our last email, but the
trajectory stands. It's almost entirely new flaky test failures or those
testing JIRAs, so we're likely replacing larger scoped "chunky" tickets
with smaller test failures, meaning we should see close-out velocity catch
up and surpass creation within the next couple cycles. All healthy signs at
this point in our release lifecycle (working through alphas) IMO.

We closed out 16 tickets in the past 11 days (
https://issues.apache.org/jira/issues/?filter=12347782&jql=project%20%3D%20cassandra%20AND%20fixversion%20in%20(4.0%2C%204.0.0%2C%204.0-alpha%2C%204.0-beta)%20AND%20resolved%20%3E%3D%20-11d%20ORDER%20BY%20priority%20DESC%2C%20assignee)
giving us a rolling 4 week total of 46, up from 37. This puts our 4 week
rolling change in the past 3 weeks at 26, 37, and now 46 - increasing close
momentum.

*Newly opened tickets*
We had 9 new tickets open in the last week that were not the epic test:
https://issues.apache.org/jira/issues/?filter=12347782&jql=project%20%3D%20cassandra%20AND%20fixversion%20in%20(4.0%2C%204.0.0%2C%204.0-alpha%2C%204.0-beta)%20AND%20created%20%3E%20-11d%20and%20resolution%20%3D%20unresolved%20and%20type%20!%3D%20epic%20and%20(%22Epic%20Link%22%20!%3D%20CASSANDRA-15536%20OR%20%22Epic%20Link%22%20is%20empty)
Of the unassigned, 5 are flaky tests and CASSANDRA-15549 is a pretty
straightforward doc / recommendation change ticket, so all good candidates
to pick up if you want to start getting more involved with the project.

*LHF / Failing Tests*: We have 8 unassigned test failures that are all
great candidates to pick up and get involved in:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&projectKey=CASSANDRA&quickFilter=1660&quickFilter=1661&quickFilter=1658

*Needs Reviewer*: 11 tickets need a reviewer. This is *up* from 7 last
time, so this is growing.
3 alpha, 1 beta, and 7 RC; I'd advocate that people take a moment to help
out with reviews if you have flexible cycles to burn that queue down.
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1659

*Available to work*: 9 alpha, 4 beta, and 14 RC tickets are available for
work (no assignee):
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&view=detail&selectedIssue=CASSANDRA-15308&quickFilter=1661&quickFilter=1658
Most of these are pretty low friction to pick up and work.

*Ready to Commit*: 4 tickets (down from 6) are marked ready to commit.
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&selectedIssue=CASSANDRA-14688&quickFilter=1672&quickFilter=1661

*Testing*:

I have a JIRA epic for tracking the cwiki status I put together; I emailed
the dev list and got some general "Lazy Consensus ftw, do what makes you
happy" style responses on it. I'll be traveling (again) this week, but I'll
see if I can't migrate the rest of the wiki into JIRA so I have a final
alpha of what it'll look like to get a final +1 on before marking the cwiki
deprecated and we can start driving assignee / reviewer / etc through this
email on the broader 4.0 testing initiatives.

Epic is here: https://issues.apache.org/jira/browse/CASSANDRA-15536

As always, thanks everyone for the time and effort you're putting into this
release specifically and the project in general. If you have any feedback
about ways I could improve the signal / value of information in this email,
please don't hesitate to let me know. My goal for this effort is to reduce
friction to contribution, save everyone's time by consolidating information
and visibility here, and help align us all on the project, so let me know
if there's something I can do to improve any of this.

Thanks again!

~Josh

Reply via email to