[OE-core] OE-Core release process

[Paul Eggleton]

On Friday 16 September 2011 18:18:43 you wrote:
> On Fri, Sep 16, 2011 at 14:16, Paul Eggleton
> 
> <paul.eggleton at linux.intel.com> wrote:
> > On Friday 16 September 2011 18:08:04 Otavio Salvador wrote:
> >> More then once I wanted to pick a patch that was in poky and not yet
> >> merged into oe-core and it wasn't that easy to split it.
> > 
> > Can you give a specific example of this?
> > 
> > Since the split, there have never been any patches intentionally merged
> > into poky's OE-core parts that were not already in OE-core. (There were
> > a few isolated occasions where some accidentally slipped in, these were
> > rectified as soon as they were discovered.)
> 
> They all ended up in oe-core the problem is when they're not yet
> merged but I want to merge them into my tree for use, test or
> anything.

Ah, so what you mean is not that the patches were in poky, but that there 
sometimes were pull requests pointing to a branch that was on top of poky. The 
thing is, the patches are exactly the same.
 
> The combo-layer was one example. It was made available on poky contrib
> tree and I had to manually export the patches instead of pulling it
> into a branch for testing.

Git makes this almost trivially easy though, and in the combo-layer example it 
was only a few patches.

Personally, I always post my OE-core pull requests on top of an OE-core 
branch; doing that means *I* have to manually bring the patches across as files 
and use git-am to apply them onto a branch of OE-core though. I think those of 
us working on Poky know this is the accepted practice and try to do it all of 
the time, occasionally someone might forget or feel that for an RFC patch it's 
not worth the effort; but I think that's the exception rather than the rule.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre