openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kurt Taylor <kurt.r.taylor@gmail.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	"Mihm, James" <james.mihm@intel.com>,
	 Brad Bishop <bradleyb@fuzziesquirrel.com>,
	sdasari@fb.com,  Ali Larijani <alirhas@microsoft.com>,
	Nancy Yuen <yuenn@google.com>,
	 Dick Wilkins <Dick_Wilkins@phoenix.com>
Subject: OpenBMC Release Planning WG Kickoff Meeting
Date: Tue, 26 Jun 2018 14:26:02 -0500	[thread overview]
Message-ID: <CAG5OiwjQA41nZP1Usj-0kk4bTWvac0mbmK=VU4jhZ2uS7W+-Jw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]

I still have not heard from Facebook or Microsoft, but the majority of
responses were for Thursday at 3:00pm Central US (2000 UTC) so we will
start there.

I will send email with the meeting info by tomorrow evening. I am stalling
in hopes that my webex account will be reactivated (it was disabled due to
a 2 week inactivity, sigh). If you have not replied, please do as I will
only invite those that reply (call info will not be made public).

I have created a wiki page for the agenda just as we have for the community
call, and I'll keep meeting minutes to send out on the list following the
meeting. Please add new agenda items in the backlog:
https://github.com/openbmc/openbmc/wiki/Release-Planning

The goal is to quickly produce a prioritized list of deliverables for our
first release this November. So, for this kickoff meeting, I'd like to see
the following:

1) Release planning representatives (primary contact)
2) Agreement on the release week in November (Nov 12-16)
3) Agreement on release numbering (OpenBMC 3.0)
4) Milestones, how many and when (design, code 1, code freeze)
5) Top 3 "Must deliver" items from each company

That is a very full agenda for an hour, so please be punctual as we will
dive right in at 3:00.

Regards,
Kurt Taylor (krtaylor)

[-- Attachment #2: Type: text/html, Size: 1562 bytes --]

             reply	other threads:[~2018-06-26 19:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26 19:26 Kurt Taylor [this message]
2018-06-26 21:01 ` OpenBMC Release Planning WG Kickoff Meeting Tao Ren
2018-06-26 21:51 ` Gunnar Mills

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='CAG5OiwjQA41nZP1Usj-0kk4bTWvac0mbmK=VU4jhZ2uS7W+-Jw@mail.gmail.com' \
    --to=kurt.r.taylor@gmail.com \
    --cc=Dick_Wilkins@phoenix.com \
    --cc=alirhas@microsoft.com \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=james.mihm@intel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=sdasari@fb.com \
    --cc=yuenn@google.com \
    /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).