openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "George Keishing" <gkeishin@in.ibm.com>
To: krtaylor <kurt.r.taylor@gmail.com>
Cc: alirhas@microsoft.com, bradleyb@fuzziesquirrel.com,
	james.mihm@intel.com,
	 "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
	"openbmc"<openbmc-bounces+gkeishin=in.ibm.com@lists.ozlabs.org>
Subject: Re: OpenBMC Release Planning Working Group
Date: Mon, 25 Jun 2018 21:05:31 +0530	[thread overview]
Message-ID: <OF271EFC9C.4E484BDD-ON002582B7.0055123F-652582B7.0055A643@notes.na.collabserv.com> (raw)
In-Reply-To: <f86c688b-b237-bdd5-12a0-385f96902581@gmail.com>

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

Hi Kurt, 

        I prefer the option 2) Thursdays, 8:00am Central US (1300 UTC) 
time. Please sign me up.  Thanks

George Keishing
 



From:   krtaylor <kurt.r.taylor@gmail.com>
To:     "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Cc:     alirhas@microsoft.com, bradleyb@fuzziesquirrel.com, 
james.mihm@intel.com
Date:   06/22/2018 12:38 AM
Subject:        OpenBMC Release Planning Working Group
Sent by:        "openbmc" 
<openbmc-bounces+gkeishin=in.ibm.com@lists.ozlabs.org>



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






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

  parent reply	other threads:[~2018-06-25 15:35 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
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 [this message]
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=OF271EFC9C.4E484BDD-ON002582B7.0055123F-652582B7.0055A643@notes.na.collabserv.com \
    --to=gkeishin@in.ibm.com \
    --cc=alirhas@microsoft.com \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=james.mihm@intel.com \
    --cc=kurt.r.taylor@gmail.com \
    --cc=openbmc-bounces+gkeishin=in.ibm.com@lists.ozlabs.org \
    --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).