Re: Branch management for OE-Core release

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Thu, 2011-09-22 at 09:49 -0300, Otavio Salvador wrote:
> I noticed the 2011-1 branch today and it seems it is not fully merged
> into master; this is a mistake since it will create an upgrade path
> problem for users of it.

Its a branch, master continues on, that branch just gets fixes suitable
for a stable/release branch. I appreciate people have different
definitions of stable and we need to do a better job of documenting what
those criteria are. As a quick attempt:

I've always said with "stable" branches, its up to the person
maintaining it to define what it means. Right now, I'm trying to get a
branch where all the Yocto QA tests pass so it has some base
functionality across all the different architectures, image targets,
SDKs and so forth.

Longer term I'm initially proposing it will take the same kinds of
changes as we'd take for point releases in Yocto. These are high impact
bug fixes, build system OS fixes as new distros appear and security
issues that we're aware of. What is out of scope are new features and
significant version changes. The QT version increment is marginal in
that regard. If after release when we have more time to test it works
out ok it might be considered being just a point release and not a major
version change.

Cheers,

Richard