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: RFC: Merging commits from into the main denzil branch
Date: Wed, 23 May 2012 15:00:48 -0700 [thread overview]
Message-ID: <4FBD5E10.3070403@intel.com> (raw)
Hello all,
As most of you know, I've been pulling commits into a pair of
sgarman/denzil-next branches which are intended to eventually become the
next Denzil point-release, 1.2.1.
oe-core based branch:
http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next
poky based branch:
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next
So far I haven't merged or requested to merge any of these commits into
the main denzil branches of oe-core and poky, for two main reasons:
1. I've only performed the most basic build testing of these branches on
a desktop system, building core-image-minimal and core-image-sato for
our 5 qemu machines.
2. To date, we haven't had a clear process on how to transition from the
maintainer's personal branch into the official repo branch. I'd like to
develop a clear and documented process on doing this that involves
community feedback on the commits.
Just this week I've been able to start using the Yocto autobuilder to do
more comprehensive testing of my denzil-next branch, so issue #1 is
finally resolved, and I've got a green build to raise my confidence level:
http://autobuilder.yoctoproject.org:8010/builders/nightly/builds/462
So now to address issue #2. The goal is to incorporate community
feedback, so I'm looking to get ACKs or NAKs for these commits before
they go into the main denzil branch.
My proposal is to send denzil pull requests to the appropriate mailing
lists, and Richard can merge them into the main repo denzil branches
once they've received review by the community.
My goal is to send these pull requests about once per week, once I've
managed to get a green build out of the Yocto autobuilder for my contrib
branch.
What do folks think about this? Now's your opportunity to offer feedback
and influence this process.
Thanks!
Scott
Yocto 1.2.1 release maintainer
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next reply other threads:[~2012-05-23 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 22:00 Scott Garman [this message]
2012-05-24 11:26 ` [yocto] RFC: Merging commits from into the main denzil branch Koen Kooi
2012-05-24 15:46 ` Scott Garman
2012-05-24 16:04 ` Koen Kooi
2012-05-24 16:54 ` Richard Purdie
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=4FBD5E10.3070403@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