From: Scott Garman <scott.a.garman@intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>, poky@yoctoproject.org
Subject: Denzil 1.2.2 development nearly complete
Date: Wed, 26 Dec 2012 09:18:44 -0800 [thread overview]
Message-ID: <50DB3174.1030709@intel.com> (raw)
Hi everyone,
I wanted to make sure the community is aware that I am wrapping things
up for our next denzil stable release, 1.2.2. We've had some discussions
about this at the Technical Team Meetings, but I thought I'd send this
out to the mailing lists as well.
The current status of my testing branches can be found here:
oe-core based tree:
http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next
and my poky-based tree:
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next
I will be submitting a pull request to Richard soon to get these patches
merged to the official denzil branches of the oe-core and poky
repositories, respectively. If anyone has outstanding patches they need
in denzil (or that I've overlooked), please get them to me as soon as
possible.
To see a list of bugs addressed during the 1.2.2 release cycle, do a
Bugzilla search for bugs with a Target Milestone of 1.2.2.
Our QA team will be back on Monday, January 7, and will begin another
full-pass test cycle on denzil. If they don't find any new bugs and can
verify the recently fixed bugs in denzil, our goal is to release 1.2.2
shortly thereafter.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
reply other threads:[~2012-12-26 17:33 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=50DB3174.1030709@intel.com \
--to=scott.a.garman@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox