Page tree
Skip to end of metadata
Go to start of metadata

Schedule

OPNFV Colorado 2.0 & 3.0 schedule

Expectations

  1. No new features should be introduced into Colorado 2.0 or 3.0.  The Feature Freeze milestone for Colorado (July 1) applies to Colorado 1.0, 2.0, and 3.0.  
  2. Colorado 2.0 and 3.0 will use the same stable branch as Colorado 1.0.  Each release will be defined by a git tag on the same branch.

Tagging

Git Tagging Instructions for Colorado Release

Documentation

  1. Any documentation released in Colorado 2.0 or 3.0 should apply to code released in a previous release, or the current release.
  2. Documentation links must be updated for each release, regardless of whether there are any changes:
  3. To update from 2.0 to 3.0 the documentation merge job must be run, this can be done by updating and merging a new documentation change, or remerging the last patchset that touched the documentation. Helpdesk will do this for you before the release if it is not done.
{project}/colorado/{version 2.0 or 3.0}/docs/{document name}
Example
moon/colorado/3.0/docs/installationprocedure
  • No labels