Added an "Epics" quick filter; could help visualize what our high priority features are for given releases:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484&quickFilter=2649 Our cumulative flow diagram of 5.0 related tickets is pretty large. Probably not a great indicator for the body of what we expect to land in the release: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484&projectKey=CASSANDRA&view=reporting&chart=cumulativeFlowDiagram&swimlane=1212&swimlane=1412&swimlane=1413&column=2116&column=2117&column=2118&column=2130&column=2133&column=2124&column=2127&from=2021-12-20&to=2023-03-09 One place we've been weak historically is in distinguishing between tickets we consider "nice to have" and things that are "blockers". We don't have any metadata that currently distinguishes those two, so determining what our burndown leading up to 5.0 looks like is a lot more data massaging and hand-waving than I'd prefer right now. I've been deep on some other issues for awhile but hope to get more involved in this space + ci within the next month or so. On Thu, Mar 9, 2023, at 9:15 AM, Mick Semb Wever wrote: >> I've also found some useful Cassandra's JIRA dashboards for previous >> releases to track progress and scope, but we don't have anything >> similar for the next release. Should we create it? >> Cassandra 4.0GAScope >> Cassandra 4.1 GA scope > > > https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484 >
