...
Discussion to revise and update the TF Release Plan
- Schedule: https://teamup.com/event/show/id/Do514LpsnNRGVg4KytEwKFsSM7SELJ6AJjHnGequMp4PNrwYRnzZWtnzhUQU
- Slides:
View file name Tungsten Fabric Release Process.pdf height 150 - Recording: Tungsten Fabric Release Planning.mp4
Minutes
Marek Chwal talked about the prerequisites
- Need engagement
- We need to build a clear project structure
- List of projects that are engaged in providing the product of TF
- Need to solve what projects we have and what they are responsible for
- Need developers registered and participating though LF resources
Currently, we have a waterfall approach. In the future, we should think about other approaches. However, we need to solve some of our initial milestones
- Marek talked about the details of the release planning https://wiki.tungsten.io/x/R4BdAQ
- Pages for the release plan have been updated
- Marek developed a template for the Feature blueprint and Project Proposals
- Talked about setting the release scope for the project.
- Krzysztof Kajkowski Where are we going to keep track of fixes intended for specific release?
- Casey asked why we would want to call the release plan for a project release a "scope". Asked if we should instead set the scope of the project based on a feature or logical grouping of features