User Tools

Site Tools


releases:releaseplanning

This is an old revision of the document!


OPNFV C release planning activities

1) Set release milestones

We need to quickly establish our key milestones for C-Release in order that projects are able to establish their scope and intentions for the release.

MS# Timeline Offset 1 Offset 2 Target
MS1 8/March 8/March 8/March Projects indicate intent toward the release
MS2 8/April 15/April 15/April Close project inclusion and establish plans
MS3 12/July 19/July 26/July Close project development phase - freeze
MS4 16/August 16/August 16/August Project release

2) Establish milestones expectations

With clear milestone dates we should work to establish the expectations on project for those milestones. The intention of this work is to ensure we have key activities done during the project work and not after code freeze.

MS1.

  • State your intention to participate in the C-Release
  • Define impacts on other projects;
    • installers
    • test projects
    • documentation
    • Infrastructure (pharos/CI)
  • Include estimated time and resource plans

MS2.

  • Have coordinated schedules with other projects and captured cross project dependencies in Jira.
  • Have a concrete project time plan in place that accommodates dependencies and resource availability
  • Dependencies must include upstream dependencies impacting ability to execute on future milestones

MS3.

  • Must be code complete.
  • Must have successfully deployed expected deliverables on a pharos lab
  • Have completed test case development
  • Have documentation in place for pre-release verification
  • Begin release readiness activities and verification.
    • Stable branch labels can be applied from here.

MS4.

  • All frozen features and scenario's have achieved release readiness.
  • All stable branch labels in place, release labels available on the branch.

3) Definition of the development process

Iterative improvements

Our development process must include alignment on key items that we want to improve from the previous release. That can be filled after the retrospective once each project are has it's list of priority improvements. Alignment to key project improvements needs to be implemented as part of the participation in the release activity.

Development processes

This may be a monthly cycle of development and scenario readiness. If such a process is used for any given release the scenario will be available from Master until such time as MS3 of the release is passed and the scenario can be migrated to stable.

This may be as in Brahmaputra where each project implemented an own project development practice. If such a process is used there needs to be clear directives on milestone deliverables that the projcts are expected to align toward in order to better manage the development effort involved in providng platform feature availability.

More…

releases/releaseplanning.1457313502.txt.gz · Last modified: 2016/03/07 01:18 by julien zhang