Return-Path: Authentication-Results: lists.ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=gmail.com (client-ip=2607:f8b0:4003:c06::235; helo=mail-oi0-x235.google.com; envelope-from=kurt.r.taylor@gmail.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="Bg9jCdR4"; dkim-atps=neutral Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 41VVWk0J4kzF3HZ for ; Wed, 18 Jul 2018 05:21:36 +1000 (AEST) Received: by mail-oi0-x235.google.com with SMTP id n84-v6so4149881oib.9 for ; Tue, 17 Jul 2018 12:21:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:message-id:date:user-agent:mime-version :content-language; bh=5+ZhEqQ1kFOM8jeQQmWxU4Xr5fZPdIm3McxfUfv9t7o=; b=Bg9jCdR4+f73NDVmGyPJm/JeWJ4iU0w0h+4kR4tcjsPcfXF/agobeGxaSjKCtUvD8W fun081tcfx1ukb9VqEXhVd5f4W0fzVYQZHulcICPYTUhYWxxR0D6B9+/WUBWnNJO8OQG 3biex/gkFcXqbfacMRrfgahiRNba9HzmsdW+KPnraOV+3JnVG4Vm71rHlIJYRkmMFKbQ 9thwq40Gw3GYf0MlJw1n1ewfcLdPCVSDxYlNT5d75D4nDhsaeQ0tcz3c8ewBQfJwCePp dUeKABlrpZ+1i+dWs74kj2fhvflWkv1NUjHaOMvocuEpBm5We3M3mk47LVKAPb3XMRYr em7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:message-id:date:user-agent :mime-version:content-language; bh=5+ZhEqQ1kFOM8jeQQmWxU4Xr5fZPdIm3McxfUfv9t7o=; b=Z70vpggYHoJgX0iGLdvN0MGcBDTFjsH4mWp53x66gpvSQeKqh7mvWLNocbDPMFTxg5 3LG48zaDYclDY8z6d1LqCf0Oyyahm4mt/6H2pP8zsw+51WVxVHEF87cbW2SFNPIL4ngK kjITfy4V+XkNW5gu6K/bWso0l0YM136v6+bg27OKFja8e9nlt23sFaMakfqHNzdq9aZe hnsDZFCVTrR5V7SbKENULKHkczn7YoixtUvgj6YkKie00YzykFsf8KTwpodsUdjf04x3 ScMbKOvxdVL8w3givLMMIsFYaywhakgCBkc8P2xoxxl9JBAT4u+76Dnq1romk6m4ZZg+ PkrA== X-Gm-Message-State: AOUpUlHoiL9flDFGBTXIQ5FkrYaRK667EC9YK8ygTobrg4Nl4iXsx9qy 2kDUcybXefhR4MLORsAlD7IjG8IE X-Google-Smtp-Source: AAOMgpepxoG/AJykUUpKu4vTLcY5gYgPn4vwl8ZNDP3qmKBYO/hi0vQT6lpra1hOYcQEfjvEq9EQsQ== X-Received: by 2002:aca:ed90:: with SMTP id l138-v6mr2946881oih.36.1531855294570; Tue, 17 Jul 2018 12:21:34 -0700 (PDT) Received: from krtaylors-MacBook-Pro.local (cpe-72-182-100-19.austin.res.rr.com. [72.182.100.19]) by smtp.gmail.com with ESMTPSA id m62-v6sm3143199oik.30.2018.07.17.12.21.33 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Jul 2018 12:21:34 -0700 (PDT) From: krtaylor Subject: 7/12 OpenBMC Release Planning WG Meeting Minutes To: "openbmc@lists.ozlabs.org" Message-ID: <781b41ee-9780-a215-c23a-375f9be8883d@gmail.com> Date: Tue, 17 Jul 2018 14:21:33 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------746B64F04277D645240031C5" Content-Language: en-US X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jul 2018 19:21:39 -0000 This is a multi-part message in MIME format. --------------746B64F04277D645240031C5 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Thanks everyone that attended - hopefully we'll have a quorum next time (July 19th). Please urge your company release planning reps to fill out the release planning spreadsheet so we can start prioritizing. Agenda for the 19th will be here: https://github.com/openbmc/openbmc/wiki/Release-Planning Meeting minutes live here: https://docs.google.com/document/d/1yo9lZp56jkwDM1eXJRE8p__FqlAjq7qcdIi1W7hAD5Y/edit?usp=sharing Kurt Taylor (krtaylor) 7/12/18 * Note: call in numbers and info may change frequently for the next few weeks, please check your email before assuming the number is the same as last week * 9 Attended o Kurt Taylor, IBM (WG lead) o Brad Bishop, IBM o *Andrew Geissler, IBM o Kun Yi, Google o Tao Ren, Facebook o Maury Zipse, IBM o Yugi Mani, Microsoft * Not attending o *Nancy Yuen, Google (on vacation) o *Sai Dasari, Facebook (on vacation) o *James Mihm, Intel (on vacation) o *Ali Larijani, Microsoft (no response) o *Dick Wilkins, Phoenix (no response) o (*) Primary company contact * Review of Agreements from previous meeting (see previous meeting minutes) * Work item prioritization spreadsheet o Company representatives need to complete their column o Process review - prioritization, public design and potential workgroup formation o Backlog: Spreadsheet needs to be completed asap o Share/Edit permissions - still problems? * Milestones, how many and when o Discussion on what milestones and why they were useful, tracking progress o Release week, code freeze o Proposed: WG formation, design, code 1, code2,...codeX, code freeze, release o Long discussion on release process/test/merge/freeze (see below) o Discussion around what was needed in each milestone o Backlog: Topic tabled for next meeting * Release process o Branching - release: branch and freeze(stop merge) and test, or branch and continue merging, but then who is testing/documenting the release? o Freeze and branch immediately so that development can continue vs. freeze/test and then branch at release date to allow for all developers to test and document o Backports to stable branches o Backlog: Supported releases, long-term support duration n-1, n-2, ... o Backlog: “Support”, what does this mean to the community? * Codenames o Brad proposed to follow Yocto, branch name would equal code name --------------746B64F04277D645240031C5 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Thanks everyone that attended - hopefully we'll have a quorum next time (July 19th). Please urge your company release planning reps to fill out the release planning spreadsheet so we can start prioritizing.

Agenda for the 19th will be here:

https://github.com/openbmc/openbmc/wiki/Release-Planning

Meeting minutes live here:

https://docs.google.com/document/d/1yo9lZp56jkwDM1eXJRE8p__FqlAjq7qcdIi1W7hAD5Y/edit?usp=sharing

Kurt Taylor (krtaylor)


7/12/18

  • Note: call in numbers and info may change frequently for the next few weeks, please check your email before assuming the number is the same as last week

  • 9 Attended

    • Kurt Taylor, IBM (WG lead)

    • Brad Bishop, IBM

    • *Andrew Geissler, IBM

    • Kun Yi, Google

    • Tao Ren, Facebook

    • Maury Zipse, IBM

    • Yugi Mani, Microsoft

  • Not attending

    • *Nancy Yuen, Google (on vacation)

    • *Sai Dasari, Facebook (on vacation)

    • *James Mihm, Intel (on vacation)

    • *Ali Larijani, Microsoft (no response)

    • *Dick Wilkins, Phoenix (no response)

    • (*) Primary company contact

  • Review of Agreements from previous meeting (see previous meeting minutes)

  • Work item prioritization spreadsheet

    • Company representatives need to complete their column

    • Process review - prioritization, public design and potential workgroup formation

    • Backlog: Spreadsheet needs to be completed asap

    • Share/Edit permissions - still problems?

  • Milestones, how many and when

    • Discussion on what milestones and why they were useful, tracking progress

    • Release week, code freeze

    • Proposed: WG formation, design, code 1, code2,...codeX, code freeze, release

    • Long discussion on release process/test/merge/freeze (see below)

    • Discussion around what was needed in each milestone

    • Backlog: Topic tabled for next meeting

  • Release process

    • Branching - release: branch and freeze(stop merge) and test, or branch and continue merging, but then who is testing/documenting the release?

    • Freeze and branch immediately so that development can continue vs. freeze/test and then branch at release date to allow for all developers to test and document

    • Backports to stable branches

    • Backlog: Supported releases, long-term support duration n-1, n-2, ...

    • Backlog: “Support”, what does this mean to the community?

  • Codenames

    • Brad proposed to follow Yocto, branch name would equal code name


--------------746B64F04277D645240031C5--