===================================================
#opnfv-release: OPNFV Release Process Working Group
===================================================


Meeting started by dmcbride at 12:55:26 UTC.  The full logs are
available at
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2018/opnfv-release.2018-10-12-12.55.log.html
.



Meeting summary
---------------

* roll call  (dmcbride, 12:55:37)
  * David McBride  (dmcbride, 12:55:44)
  * Rex  (mj_rex, 12:58:21)
  * Emma Foley  (efoley, 13:00:44)
  * Mark Beierl  (mbeierl, 13:01:51)
  * Trinath Somanchi - trinaths  (trinaths, 13:02:40)
  * Cristina Pauna  (CristinaPauna, 13:08:21)

* chair selection  (dmcbride, 13:21:06)
  * group agrees that a community member should chair the group,
    following the initial startup period  (dmcbride, 13:22:38)
  * mbeierl 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  (dmcbride, 13:23:22)
  * efoley agrees  (dmcbride, 13:26:50)

* discussion topics for upcoming meetings  (dmcbride, 13:28:22)
  * continuous delivery  (dmcbride, 13:28:46)
  * release timing for projects using CD model  (dmcbride, 13:30:14)
  * mbeierl 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  (mbeierl, 13:35:25)
  * how do we use test tools within CD process?  Test tools need
    independent validation before they can be used to validatie
    features.  (dmcbride, 13:45:12)
  * should different implementers of CD (e.g. XCI, Apex) follow a model
    (spec) so that they produce similar results for the same feature?
    (dmcbride, 13:46:36)
  * Or, should implementers follow their own design decisions with
    varying results for the same feature.  (dmcbride, 13:48:15)
  * some projects have dependency chains that may prevent them from
    participating in CD (e.g. ArmBand/Fuel depend upstream on Mirantis
    integration with openstack)  (dmcbride, 13:53:06)
  * Release gates.  How many?  What are the requirements for each?
    (dmcbride, 13:56:38)



Meeting ended at 14:01:29 UTC.



People present (lines said)
---------------------------

* dmcbride (16)
* trinaths (3)
* collabot (3)
* mbeierl (3)
* rama_y (2)
* efoley (1)
* CristinaPauna (1)
* mj_rex (1)



Generated by `MeetBot`_ 0.1.4