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 7.0 (Y/N) (1,2)

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

Intent to release 7.2 (Y/N) (1,2)
os-nosdn-nofeature-nohaApexTim RozetYYYY
os-nosdn-nofeature-haApexTim RozetYYYY
k8s-nosdn-nofeature-nohaApexTim RozetYNNN
os-odl-nofeature-nohaApexTim RozetYYYY
os-odl-nofeature-haApexYYYY
os-nosdn-nofeature-haCompassYYYY
K8-nosdn-nofeature-haCompassYYYY
os-odl-nofeature-haCompassYYY

Y

K8-nosdn-stor4nfv-haCompassYYYY
os-nosdn-bar-haCompassYYYY
os-nosdn-stor4nfv-haCompassNYYY
os-nosdn-calipso-nohaApexKoren LevNYYY
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@aarch64YNYY
os-nosdn-fdio-noha

Fuel@x86

Fuel@aarch64

YNNY
os-odl-ovs-nohaFuel@x86YYYY
os-odl-sfc-nohaXCIManuel Buil?YYY
os-odl-sfc-nohaApexYYYY
os-odl-sfc-nohaCompassYYNY
os-odl-sfc-haApexNNNY
os-odl-sfc-haCompassNNNY
os-odl-bgpvpn-nohaApexYYYY
os-odl-bgpvpn-haApexYYYY
os-odl-bgpvpn-nohaXCINNNN
os-odl-bgpvpn-haXCINNNN
os-odl-bgpvpn-nohaFuel@x86NNYY
os-nosdn-bar-ha ApexAaron SmithNNNN
os-nosdn-bar-noha ApexAaron SmithNNNN
k8-vpp-nofeature-nohaCompassNYYY
k8-nosdn-virtlet-nohaVagrantYYYY
k8-ovsdpdk-nofeature-nohaVagrantYYYY
k8-ovn-kata-nohaVagrantRuijing GuoYYYY
  • No labels