This is an old revision of the document!
The Colorado release will be framed around scenarios. Within OPNFV a scenario is a "deployment of a set of components and their configuration". Colorado will include all scenarios which are available and ready by the Colorado time frame.
We need to quickly establish our key milestones for C-Release in order that projects are able to establish their scope and intentions for the release.
MS# | Timeline | Target |
---|---|---|
Project planning start | 8/March | Projects indicate intent to participate in the release |
Planning complete | 8/April | Close project inclusion and plans are established |
Feature Code freeze | 31/Mai | Close feature project development phase - freeze |
Installation Code freeze | 21/June | Installer/plugins code complete |
Test Code freeze | 28/June | Test infra and scenario tests complete |
Integration ready | 26/July | Scenario integration complete |
Release | 16/August | Release |
With clear milestone dates we should work to establish the expectations on project for those milestones. The intention of this work is to ensure we have key activities done during the project work and not after code freeze.
MS0 : Project planning
MS1 : Planning complete
MS2 : Feature Code freeze
MS3: Installation Code freeze:
MS4: Test Code freeze
MS5: Integration ready:
MS6 : Release
Our development process must include alignment on key items that we want to improve from the previous release. That can be filled after the retrospective once each project are has it's list of priority improvements. Alignment to key project improvements needs to be implemented as part of the participation in the release activity.
This may be a monthly cycle of development and scenario readiness. If such a process is used for any given release the scenario will be available from Master until such time as MS3 of the release is passed and the scenario can be migrated to stable.
This may be as in Brahmaputra where each project implemented an own project development practice. If such a process is used there needs to be clear directives on milestone deliverables that the projcts are expected to align toward in order to better manage the development effort involved in providng platform feature availability.