At the TSC meeting today we discussed the release policy doc review in the governance repo [0] and Ian's feedback in that review. He's asked us to think about how to track work items for future releases. I volunteered to take the AR to the Release team, and we discussed it in the team meeting today. In the meeting we reviewed several options for feature tracking: * Jira - Pros: well known, full featured. Cons: Not open source, not integrated with opendev infra * Trello - Pros: free, full featured, light and easy to use Cons: Not open source, not integrated with opendev infra * Storyboard - Pros: part of opendev infra, already in use. Cons: Missing key features * Launchpad bugs - Pros: part of opendev infra, already in use. Cons: Already used for bugs, not really suited for feature tracking * Launchpad blueprints - Pros: part of opendev infra, has key features (priority, approval, owner, tracking). Cons: Not yet configured for StarlingX In the past we have used etherpads, ethercalcs and Google docs for this kind of work as well. None of those fully met our needs. I recommended to the Release team today that we adopt Launchpad Blueprints for feature tracking. This would solve several problems for the project - it would give us a way to track features, prioritize features against each other, formally approve feature content, and give the project a public work item backlog. Blueprints are used by several OpenStack teams and seem ideally suited for what we need. In fact, during the meeting we enabled the use of Blueprints for StarlingX and created a test BP. You can find it here [1]. If you want to see how other projects use Blueprints you can see an example from Nova here [2]. I've put this on the agenda for the next community meeting so we can discuss the proposal more broadly. In the meantime, the tool is available to the project. There are some policy and process issues that need to be resolved, and it may need some configuration changes. So please don't put your whole backlog into it yet, but feel free to try it out. Everyone who has access to our Launchpad bugs should have access to the Blueprints. brucej [0] https://review.opendev.org/#/c/658499/ [1] https://blueprints.launchpad.net/starlingx [2] https://blueprints.launchpad.net/nova