From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Authentication-Results: lists.ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=gmail.com (client-ip=2607:f8b0:4001:c0b::234; helo=mail-it0-x234.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="liMMHs1A"; dkim-atps=neutral Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (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 41HVNc4R9JzF1Qp for ; Sat, 30 Jun 2018 07:37:18 +1000 (AEST) Received: by mail-it0-x234.google.com with SMTP id a195-v6so4793823itd.3 for ; Fri, 29 Jun 2018 14:37:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=lj2956sriOMVzhekb0UwCugrwmDWh+1mjk+J1Jf0yH4=; b=liMMHs1A97f6jU4jo6bfcqNmp27UGqtUIvDiB3m+bJ9rq9mEHkbk+Z/Wafi+uolcX1 4leg9awTBLki+3GP/Qabsv1XyzTOeeBy0L04+mC4e67JxurjF2H56C10QE5iHqnU21ER 4fV/BXv2DGTq24Y0e1BwKJrebLDEQbE+WxOYr1vNp5C0E+84Gl0BQPaLfFl6S2Wk/0Mo JrQrothaVLLP3PlfQlg/mvlDKUrG9tJt0ZhD/kI0SocwjmESasDq5ymeSaaJeOoK81/m ZzYUslByTWmUysJOdRgfQ/KhtFVtY+LDwA2/HnnLtOc3xDgBrcO6LI+MvfYGtSotmx9z jUFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=lj2956sriOMVzhekb0UwCugrwmDWh+1mjk+J1Jf0yH4=; b=eFtEgXNpJe0/9duWuCtTv1K5bf8fre4RStShZyZG7/RhuNtISgpBPYl6nxck7HpNNq xK9CmrJKoULK+uXYK89DMA+JU+Os0qy8iMEab0NOHSQUQmAmDYYh8ffojb38oA+Sawis wFp/8vYoLBsCcnLdnjMv/V9V9D+5n9QwK/XXVI0R4Okeo/3K6IcGh0QvLM8P6w3W25A7 YNfOBJyhVc9PUjq3m5Z7KREe8GP475pYioX4y7On39O4h7T36FXENP8mWMqqXyIiIVQu FdRnWL1YLxW58SjaB/j2+9tHTSiE1o+pmvk2FiAdeCurb7L6yIklJKWw5L+ND7xVJgMP F8pA== X-Gm-Message-State: APt69E0OdOny4aTeRJyFVcZ64ql356T+Hxv+urZA9P8tzgujONK0yn73 BNnw0ebxGMiyzlv9DhDO3+QsINRrGRSu6vwAD901Rg== X-Google-Smtp-Source: AAOMgpdcsW5dU+FqDtkjCpPAJosQEaSD5pOKQ1JlqpoSahxA5LAzn+XlqlpPqnd2C2UFoXgpEyhxBWAPQtVxK6g98qY= X-Received: by 2002:a02:84cd:: with SMTP id f71-v6mr13339646jai.42.1530308235854; Fri, 29 Jun 2018 14:37:15 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac0:d481:0:0:0:0:0 with HTTP; Fri, 29 Jun 2018 14:37:15 -0700 (PDT) From: Kurt Taylor Date: Fri, 29 Jun 2018 16:37:15 -0500 Message-ID: Subject: 6/28 OpenBMC Release Planning WG Meeting Minutes To: OpenBMC Maillist Content-Type: multipart/alternative; boundary="000000000000cb8c80056fcea6b6" X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jun 2018 21:37:22 -0000 --000000000000cb8c80056fcea6b6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks again to the company representatives for a productive kickoff meeting. The meeting minutes will be kept here for now: https://docs.google.com/document/d/1yo9lZp56jkwDM1eXJRE8p__FqlAjq7qcdIi1W7h= AD5Y/edit?usp=3Dsharing Reminder: we will skip next week due to the US holiday and resume on July 12th. Kurt Taylor (krtaylor) 6/28/18 - Kickoff meeting of newly formed work group - Introductions - 9 Attended - Kurt Taylor, IBM (WG lead) - Brad Bishop, IBM - *Andrew Geissler, IBM - *James Mihm, Intel - *Dick Wilkins, Phoenix - Kun Yi, Google - Patrick Venture, Google - Tao Ren, Facebook - Maury Zipse, IBM - Not attending - *Nancy Yuen, Google (on vacation) - *Sai Dasari, Facebook (on vacation) - *Ali Larijani, Microsoft (no response) - (*) Primary company contact - Release dates - Proposed target week of November 12-16, 2018 - Discussion from Brad on release schedule being too close to Yocto release to allow for other downstream components to adopt the 2.6 rel= ease and still have time to test - Proposed to move farther after Yocto and to fall after the end of year holidays - Agreement: The first release will be in the week of January 21-25, 2019 - Agreement: The second release will be July 15-19, 2019 - Agreement: The release dates will follow every 6 months, 3 months after Yocto - Release version numbering - Proposed OpenBMC 3.0 - Brad pointed out the mapping of our release with the yocto release will be painful - Agreement: Follow Yocto release numbering, including fix builds - Agreement: OpenBMC specific build fixes will affix additional fix numbering - Major.Minor.Fix.obmc-build - For example: 2.6.4.obmc-2 - Backlog: Should we follow the Yocto codenames? Tabled for the next meeting - Milestones, how many and when - Discussion on what milestones and why they were useful, tracking progress - Proposed: WG formation, design, code 1, code2,...codeX, code freeze, release - Discussion around what was needed in each milestone and exit criteria - Discussion around what would happen if a feature didn=E2=80=99t make = a milestone - Backlog: Topic tabled for next meeting in order to get to work item discussion - Prioritized work items from each company - https://docs.google.com/spreadsheets/d/1lts-YX8J_AnS2dKfhW649OQHijz-J= RiJWHTDpKY62Hk/edit#gid=3D0 - Homework will be for each company to fill in table based on Must, Want, Nice - Must =3D must be in this release cycle - Want =3D needed feature, but lower priority, could be in the next release with some pain - Nice =3D needed feature, not important to complete this release - Backlog: Complete table, agree on top deliverables, assign leads - Next meeting - Agreement: Next meeting July 12th due to US holiday --000000000000cb8c80056fcea6b6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks again to the company representatives for = a productive kickoff meeting.=C2=A0 The meeting minutes will be kept here f= or now:

https://docs.google.com/= document/d/1yo9lZp56jkwDM1eXJRE8p__FqlAjq7qcdIi1W7hAD5Y/edit?usp=3Dsharing<= /a>

Reminder: we will skip next week due to the US holiday and resum= e on July 12th.

Kurt Taylor (krtaylor)


6/28/18

  • Kickoff meeting of n= ewly formed work group

  • Introductions

    • <= ul style=3D"margin-top:0pt;margin-bottom:0pt">

  • 9 Attended

    =

    • Kurt Taylor, = IBM (WG lead)

    • Brad Bishop, IBM

    • *Andrew Geissler, IBM

    • *James Mihm, Intel

    • *Dick Wilkins, Phoenix

    • Kun Yi, Googl= e

    • Patrick Venture, Google

    • Tao= Ren, Facebook

    • Maury Zipse, IBM

    =

  • Not attending

    • *Nancy Yuen, Google (on vacation)

    • *Sai Dasari, Facebook (on vacation)

    • *Ali Larijani= , Microsoft (no response)

  • (*) Primary company c= ontact

  • Release dates

    • Proposed target week of Novemb= er 12-16, 2018

    • Discussion from Brad on release sched= ule being too close to Yocto release to allow for other downstream componen= ts to adopt the 2.6 release and still have time to test

    • Proposed to move farther after Yocto and to fall after the end of year = holidays

    • Agreement: The first release will be in the we= ek of January 21-25, 2019

    • Agreement: The second release= will be July 15-19, 2019

    • Agreement: The release dates = will follow every 6 months, 3 months after Yocto

  • = Release version numbering

    • Proposed OpenBMC 3.0

    • =

      = Brad point= ed out the mapping of our release with the yocto release will be painful

    • Agreement: Follow Yocto release numbering, including fix = builds

    • Agreement: =C2=A0OpenBMC specific build fixes wi= ll affix additional fix numbering =C2=A0

      • Major.Minor.Fix.obmc-build

      • For example: 2.6.4.obmc-2

    • =

      = Backlog: Shou= ld we follow the Yocto codenames? Tabled for the next meeting

  • Milestones, how many and when

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

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

      <= /li>

    • Disc= ussion around what was needed in each milestone and exit criteria

    • Discussion around what would happen if a feature didn= =E2=80=99t make a milestone

    • Backlog: Topic tabled for n= ext meeting in order to get to work item discussion

    Prioritized work items from each company

  • Next meeting=

    • Agre= ement: Next meeting July 12th =C2=A0due to US holiday

    --000000000000cb8c80056fcea6b6--