[Openembedded-architecture] Stable releases and version upgrades

[Richard Purdie]

On Mon, 2019-03-18 at 14:01 +0000, Burton, Ross wrote:
> On Mon, 18 Mar 2019 at 12:49, Richard Purdie
> <richard.purdie at linuxfoundation.org> wrote:
> > My proposal is therefore that where an upstream has a stable
> > release
> > mechanism, we should work with that in OE-Core, taking direct
> > stable
> > version upgrades. We've been doing this already for the kernel and
> > recipes like openssl. I'd propose we should be doing this more
> > widely.
> > 
> > I appreciate its hard for the stable maintainer to know which
> > upstreams
> > focus on this. I therefore believe we should make a list of recipes
> > where this is acceptable, either in the policy/wiki or through
> > recipe
> > markup or some other mechanism. I don't worry too much about the
> > mechanism, we can figure that out, I do believe we need to change
> > our
> > "no upgrade" rule to be more adaptable.
> 
> I don't really have a strong opinion on the mechanics behind
> documenting the behaviour, but how do we decide what upstreams have a
> suitable stable release?  We don't want to trust every upstream that
> says they've a 'stable branch' until they can demonstrate that they
> are competent at the job.

Its going to have to be a case by case basis based on both their intent
and their history.

I think in reality it should become clear quite quickly. We're already
been doing this anyway, I just think we need to make the policy more
official.

I'm open to good way make the decision or document it...

Cheers,

Richard