On Mon, Mar 18, 2019 at 02:01:37PM +0000, Burton, Ross wrote:
> On Mon, 18 Mar 2019 at 12:49, Richard Purdie
> <[email protected]> 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.
Are we talking about automatic upgrades to the latest releases of
upstream stable branches for all such recipes, or about updating
recipes when requested?
The former would IMHO be a bad idea.
For the latter, a person testing and submitting the update plus
a mailing list review before it hits a stable branch might be
enough for avoiding bigger mistakes.
Note that there are currently bigger problems than what upstream stable
branches to trust.
It is not only boost, e.g. the recent lighttpd 1.4.50 -> 1.4.51 upgrade
in thud was an upgrade on the upstream master branch.
My impression is that the current problems are mainly due to the single
point of failure of one person alone reviewing stable changes that
are submitted through many different channels, deciding what upstreams
to trust is most of the time not a major problem.
Giving a wider audience the chance to raise objections would help the
stable maintainer to avoid mistakes.
> Ross
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
_______________________________________________
Openembedded-architecture mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-architecture
