You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Adam Holmberg <ad...@datastax.com> on 2021/02/25 22:34:43 UTC
Cassandra 4.0 Status 2021-02-25
Greetings. Here’s a quick look at Cassandra 4.0 release status for the
week. We've had lots of exciting progress on beta scope! Seven days since
last update.
Jira board with 4.0 scope:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1661
High level numbers by release phase:
Beta: 6 (-5); All in-flight;.
RC: 35 (-3);18 in-flight; Tickets stalled 7d+ is at an all-time high.
Presumably that’s because folks are focused on retiring beta scope.
Top-level metrics:
Total tickets in 4.0: 1563 (+7)
Remaining tickets represent 2.6% of total scope
Created vs. resolved trended sharply positive on this interval.
Where you can help:
* We’re within line-of-sight to closing out beta scope. Any work people can
do on remaining blockers will accelerate the project toward RC.
* 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.
In addition it is helpful to move things you’re on to “In Progress” to
avoid folks having to check in on assigned tickets in “TO DO”.
Here’s a query to check your current open+assigned items:
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:
(The same) 2 GA tickets are up for review with no reviewer
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1661&quickFilter=1659
*No assignee:
5 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
*Tickets stalled for a week:
32 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 hard work on the project.
--
Adam Holmberg
e. adam.holmberg@datastax.com
w. www.datastax.com
Re: Cassandra 4.0 Status 2021-02-25
Posted by Benedict Elliott Smith <be...@apache.org>.
Fair enough.
On 26/02/2021, 20:45, "Mick Semb Wever" <mc...@apache.org> wrote:
Should we wait for e.g. five clean CI runs in a row? Historically flaky
> tests have been a real issue for the project, and CI success probably
> shouldn't be taken instantaneously for releases.
There are tickets for flakey tests that have been pushed to fixVersion
4.0-rc intentionally, making this difficult to achieve.
A green run will be a huge achievement for the project, something we
haven't seen in a very long time. My understanding of the "we see one clean
CI run" position was taking it as a stake-in-the-ground, knowing (and
expecting) that the situation improves (with the ongoing work by many)
towards GA.
Might we instead apply the criteria on one of the rc releases before GA ?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: Cassandra 4.0 Status 2021-02-25
Posted by Mick Semb Wever <mc...@apache.org>.
Should we wait for e.g. five clean CI runs in a row? Historically flaky
> tests have been a real issue for the project, and CI success probably
> shouldn't be taken instantaneously for releases.
There are tickets for flakey tests that have been pushed to fixVersion
4.0-rc intentionally, making this difficult to achieve.
A green run will be a huge achievement for the project, something we
haven't seen in a very long time. My understanding of the "we see one clean
CI run" position was taking it as a stake-in-the-ground, knowing (and
expecting) that the situation improves (with the ongoing work by many)
towards GA.
Might we instead apply the criteria on one of the rc releases before GA ?
Re: Cassandra 4.0 Status 2021-02-25
Posted by Benedict Elliott Smith <be...@apache.org>.
Should we wait for e.g. five clean CI runs in a row? Historically flaky tests have been a real issue for the project, and CI success probably shouldn't be taken instantaneously for releases.
On 26/02/2021, 19:38, "Michael Semb Wever" <mc...@apache.org> wrote:
> * We’re within line-of-sight to closing out beta scope. Any work people can
> do on remaining blockers will accelerate the project toward RC.
So, last call for last minute concerns, the plan is to cut 4.0-rc1 once
- those beta tickets are resolved,
- the gremlins around v5 native protocol (+python driver frames) are fixed, and
- we see one clean CI run
Which looks like it might happen next week.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: Cassandra 4.0 Status 2021-02-25
Posted by Michael Semb Wever <mc...@apache.org>.
> * We’re within line-of-sight to closing out beta scope. Any work people can
> do on remaining blockers will accelerate the project toward RC.
So, last call for last minute concerns, the plan is to cut 4.0-rc1 once
- those beta tickets are resolved,
- the gremlins around v5 native protocol (+python driver frames) are fixed, and
- we see one clean CI run
Which looks like it might happen next week.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org