[Openembedded-architecture] Stable releases and version upgrades

[Adrian Bunk]

On Mon, Mar 18, 2019 at 03:21:27PM +0000, Richard Purdie wrote:
>...
> 
> There is huge pressure from people to get changes into stable quickly.
> I cannot get people to test changes in master for a time period before
> requesting backport. There is also huge pressure to accept no changes
> that break anything or impact any workflows. My personal answer to this
> has been to work on our testing, I've spent months trying to make
> things more efficient, increase coverage and better able to highlight
> problems. I don't see much other help/interest in it.
>...

Copying something I wrote in the boost discussion:

  A possible improvement would be to always use thud-next, and each time
  commits are added to thud-next an email thread with all new commits gets
  sent to the mailing list (similar to the review threads for new upstream
  stable kernels, see [1] for an example).

This usage of thud-next would mirror how master-next is used,
and sending such emails should be easy enough.

This would not replace anything else, but it would give people the 
chance to review such changes before they hit a stable branch.

There will always be grey areas and unexpected breakages, but this would 
have e.g. allowed people to tell Armin that upgrading to a new major 
release of boost in a stable branch is not a good idea.

> Cheers,
> 
> Richard

cu
Adrian

[1] https://lkml.org/lkml/2019/3/12/1290

-- 

       "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