On Wed, Dec 18, 2019 at 11:10:28AM +0000, Richard Purdie wrote: > There has been a lot of discussion about stable releases and how the > project might handle them going forward. The TSC has put together some > process/policy information on the project wiki: > > https://wiki.yoctoproject.org/wiki/LTS >...
One more comment on this: Stable/LTS common properties: - Strict “backport only”, master first policy Community status properties: - Master first policy recommended Could this be changed to the (recursive) policy When applicable, a change should already be in the next-higher maintained branch. This would include that changes backported to Yocto 3.1 LTS should already be in Yocto 3.2 community maintained. In practice it should rarely be a problem to apply a backport from master to an older release also to all releases in between, and all maintained branches are supposed to have a maintainer. > Cheers, > > Richard > (on behalf of the YP TSC) cu Adrian _______________________________________________ Openembedded-architecture mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-architecture
