1. Reassessing the Release Process TWS Meeting Feb 2 nd 2015

2. Current Simultaneous Release

3. Simultaneous Release ProsCons Perception that module is “integrated”, “official” Semi-Annual cadence with major changes happening during the timeframe Place to discuss the relationship between the projects at different milestones Significant process overhead and scalability issues Integration TestingPerception of compatibility is currently an illusion

4. Towards a “distribution” model?

5. Open Questions Is ODL a Controller Component or a Bag-of-parts? Which should it be? Can it be both? What models of ecosystem/release is desirable? Who is the target audience? Network Equipment Vendors Network Protocol experts Telco operators Enterprise Research All of Above?

6. Technical Challenges Inter-Project Dependencies Versioning Practices between projects Continuous Delivery (every commit is a potential release) SNAPSHOT Dependencies Version Management

7. Suggested Versioning Practices Need to be stored outside the build files Need to follow version range best practices within a release cycle Need to find a way to inject current versions in the build?

8. More ideas on improving process? Incremental Changes Stable versions of “core” modules System Test subsets of modules Use case specific certification New Tooling Multiple tiers of components with separable build/release Output “features” to different repositories based on component maturity? Break “offsets” into layered releases? Role of Downstream/Midstream projects e.g. OPNFV is use-case specific test/cert/deploy project Others?