Page tree
Skip to end of metadata
Go to start of metadata
  1. Scenario owners are free to delay scenario release until x.1 or x.2 as long as the requirements for MS5 have been met, OR the project has an approved MS exception for MS5.
  2. Scenario owners must support each release after their initial release.  For example, if a scenario is released in x.0, then it must also be released in x.1 and x.2. Similarly, if a scenario is released in x.1, then it must also be released in x.2.
ScenarioInstallerOwnerJenkins Job Created (Y/N)

Intent to release 8.0 (Y/N) (1,2)

Intent to release 8.1 (Y/N) (1,2)

Intent to release 8.2 (Y/N) (1,2)
os-nosdn-nofeature-nohaApexTim Rozet



os-nosdn-nofeature-haApexTim Rozet



os-odl-nofeature-nohaApexTim Rozet



os-odl-nofeature-haApexTim Rozet



k8s-nosdn-nofeature-nohaApexTim Rozet



os-nosdn-calipso-nohaApecNYYY
os-odl-sfc-nohaApexManuel Buil



os-odl-sfc-nohaXCIManuel Buil



os-odl-sfc-nohaFuelManuel Buil



os-odl-sfc-haApexManuel Buil



os-odl-sfc-haXCI



k8-multus-kata-virtlet-nohavagrantRuijing GuoNYYY
os-nosdn-nofeature-nohaFuel@x86Michael PolenchukYYYY
os-nosdn-nofeature-ha

Fuel@x86

Fuel@aarch64

Michael PolenchukYYYY
os-odl-nofeature-nohaFuel@x86YYYY
os-odl-nofeature-ha

Fuel@x86

Fuel@aarch64
Michael PolenchukYYYY
os-nosdn-ovs-nohaFuel@x86YYYY
os-nosdn-ovs-ha

Fuel@x86

Fuel@aarch64
YYYY
os-ovn-nofeature-nohaFuel@x86YYYY
os-ovn-nofeature-haFuel@aarch64YYYY
os-nosdn-fdio-noha

Fuel@x86

Fuel@aarch64

YYYY
os-odl-ovs-nohaFuel@x86YYYY
  • No labels