Based on recent discussions at the TAC level, it appears that all the communities are trying to improve their release cadence. How can we release a subset of requirements (developed and certified) prior (and so independently of) the Release Sign-Off.
Catherine Lefevre a control loop would be required - hard to represent on slide 9. perspective is that branch would occur @ RC0
Krzysztof Opasiak continousous development - freeze current and immediately branch for next release. as-is end up in a weird state that we can't enforce for next release. not all best practices are agreed to in a release because they have not been listed as requirements
Marek Chwal Product owners work the in "gray train"
Benjamin Cheung for ONAP could we ease into a transition rather then a big jump
Catherine Lefevre one approace could be to prototype with a couple of components
Robert Varga in ODL basically 3 types of projects "managed release integrated", "snapshot integrated", "self-release" . Making more and more projects release-integrated - selecting a few well understood and well staffed projects to try this out in ONAP
Dan Timoney Controller Design Studio (CDS) can pursue it's own cycle because the # of cross dependencies are limited.