All of lore.kernel.org
 help / color / mirror / Atom feed
From: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
To: "Stewart, David C" <david.c.stewart@intel.com>,
	 Richard Purdie <richard.purdie@linuxfoundation.org>,
	"'McCombe, Kevin'" <kevin.mccombe@windriver.com>,
	 "Osier-mixon, Jeffrey" <jeffrey.osier-mixon@intel.com>,
	"Fleischer, Julie N" <julie.n.fleischer@intel.com>,
	 "'paul.anderson@windriver.com'" <paul.anderson@windriver.com>,
	"Lock, Joshua" <joshua.lock@intel.com>,
	 Bruce Ashfield <bruce.ashfield@gmail.com>,
	"'Polk, Jeffrey'" <jeff.polk@windriver.com>,
	 "Zhang, Jessica" <jessica.zhang@intel.com>,
	Saul Wold <saul.wold@intel.com>,
	 "Erway, Tracey M" <tracey.m.erway@intel.com>,
	"Hohndel, Dirk" <dirk.hohndel@intel.com>,
	 "deVries, Alex" <Alex.deVries@windriver.com>,
	Mark Hatle <mark.hatle@windriver.com>,
	 "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: [ANNOUNCEMENT] Yocto Bernard 1.0 Release Candidate Readiness Review Meeting
Date: Fri, 25 Feb 2011 07:21:51 -0800	[thread overview]
Message-ID: <4D67C90F.5030007@intel.com> (raw)

All,

First, thank you everyone for all the hard work stabilizing master. As we close out the week, we enter into the next
phase of our release cycle, release candidate verification and validation. This coming weekend we will branching master
and spin the first of our release candidates for Yocto 1.0.

For the next few weeks, until we have a fully vetted gold build, we will be holding regular release readiness review
meetings. The purpose of these meetings is to go through the current release candidate and ultimately decide if it meets
release standards as set by the steering committee.

Agenda:

- Feature Status
  - Planned features yet to be pulled into master.
- Status of the Release Candidate Build
  - known build issues including sanity tests
  - status of BSP builds
- QA Status
  - number of open defects by level of importance
- Performance Status
  - build performance statistics of release candidate

Decisions:
- If feature incomplete, do we drop those features not implemented entirely attempt to fix them into existence.
- Is current performance acceptable?
- What are the current acceptable defects allowed and do we meet that.

Monday, February 28, 2011, 10:00 AM US Pacific Time
916-356-2663, Bridge: 3, Passcode: 9653542

------------------
Elizabeth Flanagan
Yocto Project
Release Engineer


                 reply	other threads:[~2011-02-25 15: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=4D67C90F.5030007@intel.com \
    --to=elizabeth.flanagan@intel.com \
    --cc=Alex.deVries@windriver.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=david.c.stewart@intel.com \
    --cc=dirk.hohndel@intel.com \
    --cc=jeff.polk@windriver.com \
    --cc=jeffrey.osier-mixon@intel.com \
    --cc=jessica.zhang@intel.com \
    --cc=joshua.lock@intel.com \
    --cc=julie.n.fleischer@intel.com \
    --cc=kevin.mccombe@windriver.com \
    --cc=mark.hatle@windriver.com \
    --cc=paul.anderson@windriver.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=saul.wold@intel.com \
    --cc=tracey.m.erway@intel.com \
    --cc=yocto@yoctoproject.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.