David McBride to locate CD process documentation from the last plugfest

Release requirements need to be defined per type of project

test projects need to be validated separately, so that the validation they provide is credible

October 12, 2018

Agenda

Working group purpose

Meeting logistics (time, frequency, etc.)

Chair selection

Discussion topics and priority

Minutes

Introduction and Purpose

David McBride discusses need for TSC level group to drive updates and changes to OPNFV release process

The RPWG will look at process at a high level, as opposed to the regular release meeting which deals with the day-to-day issues of executing the current release process

Important issues to be addressed:

CD process

Better accommodation of non-feature projects that do not deploy a scenario (e.g., test frameworks and tools)

Chair selection

Group agrees that a community member should chair the group, following the initial startup period

Mark Beierl suggests that if we can't find someone to commit to being the chair, then a fallback would be to rotate the chair among members of the working group. Emma Foley agrees.

Discussion topics for upcoming meetings

continuous delivery

release timing for projects using CD model(

Mark Beierl suggests CI/CD releases should not have branches as we will not go back to old versions to fix a bug and release that as a branched version.

CI/CD releases always move forward and new features along with bug fixes are always put on the new release. Only traditional release has bug fix branches

how do we use test tools within CD process? Test tools need independent validation before they can be used to validatie features

Should different implementers of CD (e.g. XCI, Apex) follow a model (spec) so that they produce similar results for the same feature?Or, should implementers follow their own design decisions with varying results for the same feature.

some projects have dependency chains that may prevent them from participating in CD (e.g. ArmBand/Fuel depend upstream on Mirantis integration with openstack)

Release gates. How many? What are the requirements for each?

No labels

Overview

Content Tools

Powered by a free Atlassian Confluence Open Source Project License granted to Open Platform for NFV (OPNFV). Evaluate Confluence today.