You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Jon Meredith <jm...@gmail.com> on 2020/12/07 19:08:28 UTC
Cassandra 4.0 Status 2020-12-07
It's been three weeks since the last status update, so here's where we are.
Jira board with 4.0 scope:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1661
High level numbers by release phase:
Alpha: 1 (-1 from last update); Last ticket from alpha,
CASSANDRA-13701 lowering default num_tokens in review, related to the
CASSANDRA-16079 Improve dtest runtime.
Beta: 55 (+2 from last update); 31 in-flight, no blockers. 15 tasks
show up in the 7-day stall.
RC: 20 (-6 from last update);
Created vs. resolved continues to trend positively:
https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=filter-12347782&periodName=daily&daysprevious=45&cumulative=true&versionLabels=major&selectedProjectId=12310865&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Acreatedvsresolved-report&atl_token=A5KQ-2QAV-T4JA-FDED_a3bea645259beee42ed00c68f87626d5972705c4_lin&Next=Next
Where you can help:
* Each filter referenced below depends on accurate assignments in
Jira. In addition to actively assigning something you’re working on,
it would also be helpful to review and unassign (both Reviewer and
Assignee) things that you have assigned but may not be able to work on
in the release timeline.
Here’s a query to check that for yourself:
https://issues.apache.org/jira/issues/?filter=12348585&jql=project%20%3D%20cassandra%20AND%20fixversion%20in%20(4.0%2C%204.0.0%2C%204.0-alpha%2C%204.0-beta%2C%204.0-rc%2C%204.0-alpha1%2C%204.0-alpha2%2C%204.0-alpha3%2C%204.0-alpha4%2C%204.0-alpha5%2C%204.0-alpha6%2C%204.0-beta-1%2C%204.0-beta1%2C%204.0-beta2%2C%204.0-beta3%2C%204.0-beta4)%20AND%20(resolution%20%3D%20unresolved%20OR%20status%20!%3D%20resolved)%20and%20(assignee%20%3D%20currentUser()%20or%20reviewer%20%3D%20currentUser()%20or%20reviewers%20%3D%20currentUser())%20
*Needs Reviewer:
1 Beta and 1 RC issues are awaiting review without reviewers.
Timely reviews here obviously keep things flowing, and help by keeping
the changes fresh in the patch contributor’s mind.
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1661&quickFilter=1659
*No assignee:
10 Beta and 4 RC issues
Please take a look and see if it’s within your capacity to take any of these on:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1661&quickFilter=1658
*Test analysis and shepherding. We possibly have a fair amount of
unaccounted scope in the Quality/Test tickets that have not been
analyzed and expanded into subtasks.
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1939
Anything we can do to expedite that will give us a better picture of
what’s left, as well as allow us to parallelize test creation. Good
examples of those that have been broken down are the metrics and
tooling areas:
https://issues.apache.org/jira/browse/CASSANDRA-15582
https://issues.apache.org/jira/browse/CASSANDRA-15583
There are numerous similar tickets remaining.
*Tickets stalled for a week:
1 alpha, 10 beta, 8 GA
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1661&quickFilter=1694
Please let us know on the thread if I have missed anything that needs
attention. I encourage anyone to respond to these reports calling
attention to any localized things that could use it.
As always thanks to everyone for the continued work on the project.
-Jon Meredith
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: Cassandra 4.0 Status 2020-12-07
Posted by Adam Holmberg <ad...@datastax.com>.
Hey folks. I appreciate the pulse these emails lend to this release, but at
times they can be a bit sobering. While things continue to be pointed in
the right direction, you can see it’s been a bit of a slog and it got me
wondering “when might 4.0 be done?”. I did a little Jira digging to use
recent history as evidence of bandwidth, and create a projection including
the following assumptions:
-
Holidays degrade December and January production (Jan to a lesser degree)
-
Aside from that, stakeholders continue to direct the same energy and
resource
-
We will see more ticket expansion as QA Testing headlines are decomposed
into sub-tasks
-
The rate of bug/flaky test tickets optimistically diminishes as we are
stabilizing and adding tests around existing functionality
Obviously, as with any projection there is a bit of hand-waving. I’m happy
to discuss my methodology more, but without getting into the weeds I just
thought I’d toss it out for discussion:
This model has 4.0 bottoming out on tickets at approximately the end of
March.
Now I’m curious: how does this align with others’ expectations? Is this
timeline acceptable? Does anyone have, or know of any plans that would
change this significantly?
I’m interested to hear how this strikes you.
On Mon, Dec 7, 2020 at 1:08 PM Jon Meredith <jm...@gmail.com> wrote:
> It's been three weeks since the last status update, so here's where we are.
>
> Jira board with 4.0 scope:
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1661
>
> High level numbers by release phase:
>
> Alpha: 1 (-1 from last update); Last ticket from alpha,
> CASSANDRA-13701 lowering default num_tokens in review, related to the
> CASSANDRA-16079 Improve dtest runtime.
>
> Beta: 55 (+2 from last update); 31 in-flight, no blockers. 15 tasks
> show up in the 7-day stall.
>
> RC: 20 (-6 from last update);
>
> Created vs. resolved continues to trend positively:
>
> https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=filter-12347782&periodName=daily&daysprevious=45&cumulative=true&versionLabels=major&selectedProjectId=12310865&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Acreatedvsresolved-report&atl_token=A5KQ-2QAV-T4JA-FDED_a3bea645259beee42ed00c68f87626d5972705c4_lin&Next=Next
>
>
> Where you can help:
>
> * Each filter referenced below depends on accurate assignments in
> Jira. In addition to actively assigning something you’re working on,
> it would also be helpful to review and unassign (both Reviewer and
> Assignee) things that you have assigned but may not be able to work on
> in the release timeline.
>
> Here’s a query to check that for yourself:
>
>
> https://issues.apache.org/jira/issues/?filter=12348585&jql=project%20%3D%20cassandra%20AND%20fixversion%20in%20(4.0%2C%204.0.0%2C%204.0-alpha%2C%204.0-beta%2C%204.0-rc%2C%204.0-alpha1%2C%204.0-alpha2%2C%204.0-alpha3%2C%204.0-alpha4%2C%204.0-alpha5%2C%204.0-alpha6%2C%204.0-beta-1%2C%204.0-beta1%2C%204.0-beta2%2C%204.0-beta3%2C%204.0-beta4)%20AND%20(resolution%20%3D%20unresolved%20OR%20status%20!%3D%20resolved)%20and%20(assignee%20%3D%20currentUser()%20or%20reviewer%20%3D%20currentUser()%20or%20reviewers%20%3D%20currentUser())%20
>
> *Needs Reviewer:
>
> 1 Beta and 1 RC issues are awaiting review without reviewers.
>
> Timely reviews here obviously keep things flowing, and help by keeping
> the changes fresh in the patch contributor’s mind.
>
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1661&quickFilter=1659
>
> *No assignee:
>
> 10 Beta and 4 RC issues
>
> Please take a look and see if it’s within your capacity to take any of
> these on:
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1661&quickFilter=1658
>
> *Test analysis and shepherding. We possibly have a fair amount of
> unaccounted scope in the Quality/Test tickets that have not been
> analyzed and expanded into subtasks.
>
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1939
>
> Anything we can do to expedite that will give us a better picture of
> what’s left, as well as allow us to parallelize test creation. Good
> examples of those that have been broken down are the metrics and
> tooling areas:
>
> https://issues.apache.org/jira/browse/CASSANDRA-15582
> https://issues.apache.org/jira/browse/CASSANDRA-15583
>
> There are numerous similar tickets remaining.
>
> *Tickets stalled for a week:
>
> 1 alpha, 10 beta, 8 GA
>
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1661&quickFilter=1694
>
>
> Please let us know on the thread if I have missed anything that needs
> attention. I encourage anyone to respond to these reports calling
> attention to any localized things that could use it.
>
> As always thanks to everyone for the continued work on the project.
>
> -Jon Meredith
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
>
--
Adam Holmberg
e. adam.holmberg@datastax.com
w. www.datastax.com