From: krtaylor <kurt.r.taylor@gmail.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: 7/12 OpenBMC Release Planning WG Meeting Minutes
Date: Tue, 17 Jul 2018 14:21:33 -0500 [thread overview]
Message-ID: <781b41ee-9780-a215-c23a-375f9be8883d@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2916 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 25304 bytes --]
reply other threads:[~2018-07-17 19:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=781b41ee-9780-a215-c23a-375f9be8883d@gmail.com \
--to=kurt.r.taylor@gmail.com \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).