User Tools

Site Tools


releases:releaseplanning

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
releases:releaseplanning [2016/03/22 17:36]
Christopher Price
releases:releaseplanning [2016/03/22 20:34] (current)
Frank Brockners [Release Structure for Colorado (Proposal)]
Line 5: Line 5:
 The Colorado release will be framed around scenarios. Colorado will include all scenarios which are available and ready by the Colorado time frame. The Colorado release will be framed around scenarios. Colorado will include all scenarios which are available and ready by the Colorado time frame.
  
-{{:​releases:​opnfv_release_and_scenario_releases.pdf|Overview presentation of scenario ​releases.}} (presented at OPNFV Hackfest, Santa Clara, March 14-15, 2016).+{{:​releases:​opnfv_release_and_scenario_releases.pdf|Overview presentation of scenario ​editions.}} (presented at OPNFV Hackfest, Santa Clara, March 14-15, 2016).
  
  
Line 27: Line 27:
     * Not all scenarios are of the same complexity: Allow for per scenario schedules; allow scenarios to define their own schedule     * Not all scenarios are of the same complexity: Allow for per scenario schedules; allow scenarios to define their own schedule
   * Scenario availabilty:​   * Scenario availabilty:​
-    * Frequently (once per month) ​release ​scenarios (i.e. publish results of deployment and testing) ​which are ready (i.e. pass the release criteria)+    * Frequently (once per month) ​make completed ​scenarios ​available ​(i.e. publish results of deployment and testing).
       * //Note: This is confusing, to whom is it published and to whom is this release targeted from a scenario every month? ​ The monthly scenarion schedule seems unneccessary,​ scenario'​s can be available when they are available without needing to establish a schedule.//       * //Note: This is confusing, to whom is it published and to whom is this release targeted from a scenario every month? ​ The monthly scenarion schedule seems unneccessary,​ scenario'​s can be available when they are available without needing to establish a schedule.//
     * Scenario schedules work in parallel to macro OPNFV release schedule     * Scenario schedules work in parallel to macro OPNFV release schedule
-    * Scenario ​releases ​fold into the next OPNFV release: All scenarios which are *interested* in joining a release and are *ready* (i.e. scenarios deploy, test results are accepted, documentation is available) participate in a release. ​+    * Completed ​Scenario fold into the next OPNFV release: All scenarios which are *interested* in joining a release and are *ready* (i.e. scenarios deploy, test results are accepted, documentation is available) participate in a release. ​
       * Scenarios which participate in a release commit to also maintain the released status (i.e. create a stable branch and maintain the branch until the next release)       * Scenarios which participate in a release commit to also maintain the released status (i.e. create a stable branch and maintain the branch until the next release)
 +        * This includes aligning with the maintenance planning for all associated and dependent projects. (installer, test project release and maintenance plans etc...)
       * "​Experimental scenarios":​ Scenarios can choose to not participate in a release (e.g. scenario is to only provide feedback at a given point in time to upstream project and does not intend to maintain a particular composition longer term. This could e.g. be the case for a test scenario is being stood up to figure out a particular integration - and once stable, the scenario would be merged with an already existing scenario).       * "​Experimental scenarios":​ Scenarios can choose to not participate in a release (e.g. scenario is to only provide feedback at a given point in time to upstream project and does not intend to maintain a particular composition longer term. This could e.g. be the case for a test scenario is being stood up to figure out a particular integration - and once stable, the scenario would be merged with an already existing scenario).
  
Line 47: Line 48:
   * An OPNFV release consists of a set of scenarios which are "ready for release"​.   * An OPNFV release consists of a set of scenarios which are "ready for release"​.
   * The Genesis project defines a common baseline for install-features and user-experience for a particular release. Through the Genesis project a common denominator across different deployments for a particular release is ensured.   * The Genesis project defines a common baseline for install-features and user-experience for a particular release. Through the Genesis project a common denominator across different deployments for a particular release is ensured.
-  * OPNFV releases have a set of milestones - some of which they share with scenarios which provides some level of synchronization between scenario ​releases ​and OPNFV releases. Note that a complete synchronization of milestones isn't desirable, because it would lead to global synchronization and thus the slowest scenario or component would determine the overall speed (Brahmaputra already departed from a monolithic, fully synchronized release process). Global milestones could include:+  * OPNFV releases have a set of milestones - some of which they share with scenarios which provides some level of synchronization between scenario ​editions ​and OPNFV releases. Note that a complete synchronization of milestones isn't desirable, because it would lead to global synchronization and thus the slowest scenario or component would determine the overall speed (Brahmaputra already departed from a monolithic, fully synchronized release process). Global milestones could include:
     * Release planning complete     * Release planning complete
     * Scenarios definition (that desire to participate in the release) complete     * Scenarios definition (that desire to participate in the release) complete
releases/releaseplanning.1458668161.txt.gz ยท Last modified: 2016/03/22 17:36 by Christopher Price