From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: yocto 1.3 branch for meta-openembedded layers, RFC wanted.
Date: Thu, 25 Oct 2012 12:55:47 +0200 [thread overview]
Message-ID: <k6b5r8$edu$1@ger.gmane.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
We need a branch to track oe-core 'danny' and I am swamped till ELC-E
happens, so I would like to hold off on patches that make meta-oe layers
incompatible with oe-core 'danny'.
As for branch maintenance: any volunteers for managing the meta-openembedded
'danny' branches? There doesn't need to be a single maintainer, but it would
be nice to have one person coordinating everything, even if it's just
pulling in danny-next branches from the layer maintainers every week or so.
As I said above, I'm swamped for the next 3 weeks, so can people who have
used or are using the 'denzil' branch weigh in with feedback/anecdotes/etc?
I have such a document for oe-core 'denzil', which I keep failing to send
out, but it boils down to "better predictability for merge windows". Please
share your experience for meta-oe here.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFQiRqzMkyGM64RGpERAschAJ98yscNYLI9qNGRviDm+drBquLttACgoa0X
/YhGdFr+iYLy8n99sXb4zKE=
=ahtL
-----END PGP SIGNATURE-----
next reply other threads:[~2012-10-25 11:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 10:55 Koen Kooi [this message]
2012-10-25 19:09 ` yocto 1.3 branch for meta-openembedded layers, RFC wanted Martin Jansa
2012-10-26 15:14 ` Khem Raj
2012-11-21 15:20 ` Eric Bénard
2012-11-21 13:11 ` Philip Balister
2012-11-21 13:26 ` Martin Jansa
2012-11-21 15:17 ` Eric Bénard
2012-11-21 16:34 ` Khem Raj
2012-11-21 20:28 ` Otavio Salvador
2012-11-22 8:53 ` Koen Kooi
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='k6b5r8$edu$1@ger.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.openembedded.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.