All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Mihm <james.mihm@gmail.com>
To: krtaylor <kurt.r.taylor@gmail.com>
Cc: openbmc@lists.ozlabs.org, alirhas@microsoft.com,
	 Brad Bishop <bradleyb@fuzziesquirrel.com>,
	"Mihm, James" <james.mihm@intel.com>
Subject: Re: OpenBMC Release Planning Working Group
Date: Fri, 22 Jun 2018 16:24:48 -0700	[thread overview]
Message-ID: <CADy_Pt1f5Fom5H_TO-sgE_Lx=wu9KJLG0qR3pF81rrihkzKgSA@mail.gmail.com> (raw)
In-Reply-To: <f86c688b-b237-bdd5-12a0-385f96902581@gmail.com>

My vote is for the 2pm or 3pm slots.

1) Tuesdays, 2:00pm Central US (1900 UTC)
  - or -
3) Thursdays, 3:00pm Central US (2000 UTC)
On Thu, Jun 21, 2018 at 12:08 PM krtaylor <kurt.r.taylor@gmail.com> wrote:
>
> Hi all,
>
> The long anticipated OpenBMC Release Planning working group is now
> forming and will have its first meeting next week. I would like to keep
> the meeting small at first so that we can move quickly, but I do need
> complete representation. Please let me know if you'd like to participate
> and what day a meeting would work best for you. Those on copy should
> plan on attending or at least make sure someone is covering for your
> organization.
>
> Let me know if you have any questions.
>
> Regards, Kurt Taylor (krtaylor)
>
>
> Proposed times:
>
> 1) Tuesdays, 2:00pm Central US (1900 UTC)
>
> 2) Thursdays, 8:00am Central US (1300 UTC)
>
> 3) Thursdays, 3:00pm Central US (2000 UTC)
>
>
> Initial Agenda:
>
> 1) Agree on the release process and set an initial release date in
> November (see email from May 21)
>
> 2) Set design and freeze milestones
>
> 3) "Must" deliver items for November release
>
> 4) How to open the design and development for a needed feature
>

  parent reply	other threads:[~2018-06-22 23:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-21 19:07 OpenBMC Release Planning Working Group krtaylor
2018-06-22  4:26 ` Sivas Srr
2018-06-22 23:24 ` James Mihm [this message]
2018-06-24 13:27 ` Brad Bishop
2018-06-25 15:13   ` Nancy Yuen
2018-06-25 15:22 ` Andrew Geissler
2018-06-25 15:35 ` George Keishing
2018-06-25 19:06   ` Patrick Venture
2018-06-26 16:37     ` Kurt Taylor
2018-06-26 16:45       ` Patrick Venture
2018-06-26 17:05       ` Kun Yi

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='CADy_Pt1f5Fom5H_TO-sgE_Lx=wu9KJLG0qR3pF81rrihkzKgSA@mail.gmail.com' \
    --to=james.mihm@gmail.com \
    --cc=alirhas@microsoft.com \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=james.mihm@intel.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.