Skip to end of metadata
Go to start of metadata

CPerf Colorado Release Plan

Release plan for the first OPNFV release CPerf has taken part in, Colorado.

Release Priorities

CPERF-1 - Getting issue details... STATUS

CPERF-2 - Getting issue details... STATUS

CPERF-3 - Getting issue details... STATUS

CPERF-4 - Getting issue details... STATUS

Dependencies

Primary:

  • Apex installer with the most recent version of OpenDaylight they can provide.
  • Pharos infrastructure, standard.

Stretch:

  • Apex installer with non-OpenDaylight SDN controller (CERF-4).
  • Other installers.
  • Integrations with Yardstick or FuncTest.

Milestone 0

Colorado MS0 Planning Artifacts

Milestone 1

Colorado MS1 Planning Artifacts

Schedule

See the main Colorado Release Plan.

In the MS1 report we were asked for an "estimated feature freeze date for your project". We suspect our development will look more like a rolling release, where it's best just to take the latest version of our code.

Blocking Bugs

None

Contact

Primary contact is the CPerf PTL.

  • Daniel Farrell (dfarrell@redhat.com, IRC: dfarrell07)

Secondary contacts are the other CPerf committers.

  • Luis Gomez (ecelgp@gmail.com, IRC: LuisGomez)
  • Jamo Luhrsen (jluhrsen@redhat.com, IRC: jamoluhrsen)
  • Marcus Williams (marcus.williams@intel.com, IRC: mgkwill)
  • Tim Rozet (trozet@redhat.com, IRC: trozet)

CPerf can also be contacted via the #opnfv-cperf Freenode IRC channel or the opnfv-tech-discuss mailing list with the `[cperf]` tag.

CPerf holds quick, informal weekly meetings. See meetings/cperf for details.

  • No labels