From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] qt4: update to latest version 4.7.4
Date: Fri, 16 Sep 2011 13:54:29 +0100 [thread overview]
Message-ID: <1316177670.3510.31.camel@phil-desktop> (raw)
In-Reply-To: <4E733F7D.6090109@eukrea.com>
On Fri, 2011-09-16 at 14:22 +0200, Eric Bénard wrote:
> I don't understand why oe-core's development has to be stopped by yocto's
> releases process but I may not have found the right page on the wiki
> explaining all the details : may you please give me some links concerning this
> policy ?
It does seem a little bit strange, yes. If it's just a short period
then I don't think there should be any real problem with granting yocto
a short freeze in oe-core so that they can do their branching.
Of course, this isn't going to scale very well if every user of oe-core
starts asking for a development freeze so that they can cut their own
release branches, and it isn't totally obvious to me that yocto couldn't
just as easily have branched from some semi-arbitrary point and then
cherry-picked or reverted a few changes to get to where they wanted.
Possibly the intent is to make a standalone release of oe-core itself on
the back of whatever yocto ends up shipping, I dunno. That seems like
it might be a reasonable enough way to get a version of OE-core that
other people can build on without having to repeat all the QA and
release engineering work that yocto are presumably doing for themselves.
But at the end of the day, I guess, it's Richard's tree and he is
perfectly entitled to freeze it whenever he wishes. OE-core is still
quite a young project and it seems sensible enough to try different
things and see what works.
p.
next prev parent reply other threads:[~2011-09-16 12:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-10 20:07 [PATCH 1/2] qt4: add blacklist-diginotar-certs patch Eric Bénard
2011-09-10 20:07 ` [PATCH 2/2] qt4: update to latest version 4.7.4 Eric Bénard
2011-09-11 17:22 ` Anders Darander
2011-09-11 17:33 ` [PATCH] " Eric Bénard
2011-09-12 10:34 ` Paul Eggleton
2011-09-14 11:11 ` Koen Kooi
2011-09-14 13:09 ` Eric Bénard
2011-09-14 15:34 ` Otavio Salvador
2011-09-15 7:57 ` Eric Bénard
2011-09-15 15:07 ` Otavio Salvador
2011-09-14 17:03 ` Koen Kooi
2011-09-15 17:32 ` Saul Wold
2011-09-15 18:41 ` Eric Bénard
2011-09-15 20:06 ` Otavio Salvador
2011-09-16 11:12 ` Paul Eggleton
2011-09-16 12:22 ` Eric Bénard
2011-09-16 12:54 ` Phil Blundell [this message]
2011-09-16 16:46 ` Richard Purdie
2011-09-16 13:11 ` Otavio Salvador
2011-09-19 9:45 ` Koen Kooi
2011-09-19 11:48 ` Otavio Salvador
2011-09-19 12:09 ` Koen Kooi
2011-09-19 12:25 ` Otavio Salvador
2011-09-19 13:03 ` Richard Purdie
2011-09-19 19:33 ` Eric Bénard
2011-09-20 21:18 ` Eric Bénard
2011-09-21 10:44 ` Koen Kooi
2011-09-21 12:52 ` Eric Bénard
2011-09-21 13:05 ` Koen Kooi
2011-09-21 13:16 ` Eric Bénard
2011-09-28 10:11 ` Paul Eggleton
2011-09-28 10:23 ` Eric Bénard
2011-09-28 13:11 ` Otavio Salvador
2011-09-28 13:33 ` Richard Purdie
2011-09-30 11:47 ` Eric Bénard
2011-09-30 16:23 ` Paul Eggleton
2011-09-12 10:34 ` [PATCH 1/2] qt4: add blacklist-diginotar-certs patch Paul Eggleton
2011-09-15 17:34 ` Saul Wold
-- strict thread matches above, loose matches on Subject: below --
2011-09-15 8:40 [PATCH] qt4: update to latest version 4.7.4 Eric Bénard
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=1316177670.3510.31.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox