* 6/28 OpenBMC Release Planning WG Meeting Minutes
@ 2018-06-29 21:37 Kurt Taylor
0 siblings, 0 replies; only message in thread
From: Kurt Taylor @ 2018-06-29 21:37 UTC (permalink / raw)
To: OpenBMC Maillist
[-- Attachment #1: Type: text/plain, Size: 3606 bytes --]
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__FqlAjq7qcdIi1W7hAD5Y/edit?usp=sharing
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 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 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’t 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-JRiJWHTDpKY62Hk/edit#gid=0
-
Homework will be for each company to fill in table based on Must,
Want, Nice
-
Must = must be in this release cycle
-
Want = needed feature, but lower priority, could be in the next
release with some pain
-
Nice = 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
[-- Attachment #2: Type: text/html, Size: 31378 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-06-29 21:37 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-06-29 21:37 6/28 OpenBMC Release Planning WG Meeting Minutes Kurt Taylor
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).