> It looks like the swimline for "Patch 5.0.x" is missing. Ugh. Thanks for pointing that out. Should be fixed now.
The swimlane was configured but tickets were getting caught up in an earlier lane. We have to decide where we want a ticket to live that has, for example, FixVersions (4.1.x, 5.0.x, 6.x). For now, **I've configured things so tickets will show up in the oldest release version to which they apply**, with the understanding that we merge all work forward to trunk unless otherwise specified. A couple things that stand out from this filtering: • Next major is heavy at 608 issues • Patch 5.0.x has 119 issues • Patch 3.x still has 251 issues; we should triage these to see what needs to be dropped and pulled forward • "Missing Version" has 1845 issues; worth it to triage these I think. I've added the following quick filters up top as well to focus the board on certain workflows: • Core Cassandra: limits to PROJECT = CASSANDRA only • EOL FixVersion: limits to tickets w/fixversion targeting out of support C* versions (251 mentioned above, 8 tickets target 5.0.x have an EOL fixversion as well) • Missing Version: tickets w/out versions. 1845 in Core Cassandra, dozens in various ecosystem projects On Sat, May 17, 2025, at 10:35 AM, Mick Semb Wever wrote: > . > > On Fri, 16 May 2025 at 20:53, Josh McKenzie <jmcken...@apache.org> wrote: >> __ >> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484 >> > > > > Nice, thank you Josh. > > It looks like the swimline for "Patch 5.0.x" is missing. >
