From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: OE-Core release process
Date: Fri, 16 Sep 2011 17:51:53 +0100 [thread overview]
Message-ID: <1316191921.20858.43.camel@ted> (raw)
In-Reply-To: <CAP9ODKor_37hXUvXv3GOYkF1ugkC_sWK4i4SW7tiU8ekJYu6Dw@mail.gmail.com>
On Fri, 2011-09-16 at 10:29 -0300, Otavio Salvador wrote:
> On Fri, Sep 16, 2011 at 09:54, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > Its been mentioned to me that we perhaps haven't made it really clear
> > what is happening with OE-Core at the moment. When we started this off,
> > we agreed to try and get on a roughly six month release cadence so
> > people had some idea of what to expect from the project and when. We
> > decided to put that in sync with what Yocto was doing since it was felt
> > OE-Core would equally benefit from the QA and bug fixing Yocto does as
> > part of its release process.
>
> I fully agree on that and I do think this will gonna be good for both
> projects; what I dislike is that Yocto people keep using Poky to their
> development instead of OE-Core and this it is quite boring to share
> patches between both until you have cherry-pick them.
>
> This should be change in my point of view and people ought to use
> oe-core for hacking so we all share same base tree.
The shr people keep using their shr scripts and tree and angstrom do the
same to pick two examples. No, we're not all going to use OE-Core alone,
that was never the point. So why should we single out poky either? Ok, a
lot of patches are coming from there but that's good, right? :)
I've yet to refuse a bug report on the grounds of "not OE-Core alone"
and don't plan to start :)
The patches do translate easily, if they didn't I'd be going (more)
insane!
Cheers,
Richard
next prev parent reply other threads:[~2011-09-16 16:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 12:54 OE-Core release process Richard Purdie
2011-09-16 13:29 ` Otavio Salvador
2011-09-16 16:51 ` Richard Purdie [this message]
2011-09-16 17:08 ` Otavio Salvador
2011-09-16 17:16 ` Paul Eggleton
2011-09-16 17:18 ` Otavio Salvador
2011-09-16 17:49 ` Paul Eggleton
2011-09-16 19:06 ` Otavio Salvador
2011-09-16 19:45 ` Mark Hatle
2011-09-16 20:51 ` Otavio Salvador
2011-09-17 2:55 ` Chris Larson
2011-09-17 9:06 ` Koen Kooi
2011-09-17 12:05 ` Otavio Salvador
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=1316191921.20858.43.camel@ted \
--to=richard.purdie@linuxfoundation.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