https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484
I've done the following: 1. added all the cassandra subprojects into the base query that feeds the board 2. added swimlanes for the various ecosystem projects (including a 1.0 release lane for analytics and sidecar) 3. added quick filters at the top where you can narrow things down to different subprojects. Of particular interest: you can now filter down to just ecosystem tickets, just analytics, just sidecar, etc. 4. Updated FixVersion on a bunch of analytics tickets that are considered "blockers" for the 1.0 release This motion of "how far do we need to bring a project to have a 1st class 1.0 release" is different than our regular "I hope to get this feature into the next release N, so I'm going to flag as FixVersion "N.X". After 1.0 on any given subproject I expect we'll naturally move to the "N.X" FixVersion paradigm. A few of us are currently working through the backlog on getting sidecar tickets and metadata cleaned up in JIRA and aligned to a 1.0 release roadmap to collaborate on on the dev list - a similar exercise to what Doug drove on Analytics. After the Sidecar 1.0 work is reflected in JIRA and we open discussion on the dev list / call to action, I'm planning on opening a [DISCUSS] thread about what we want to do for our next major on the core DB so expect to see that next week sometime. Filtering down to just showing Epics is interesting - gives a high level overview of some things (though I have no doubt we have things not reflected here, ticket statuses aren't necessarily accurate, etc): https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484&quickFilter=2649 Please let me know if any of you have any trouble accessing things; there's ~ 3.3k JIRA tickets that qualify under the base query from pulling the entire ecosystem together like this but it seems to be behaving itself just fine for me. Feature requests and improvement requests welcome. :) ~Josh
