[yocto] [Openembedded-architecture] [RFC] stable branch naming scheme

[Denys Dmytriyenko]

On Fri, Nov 03, 2017 at 09:20:43AM -0700, akuster808 wrote:
> Hello,
> 
> The problem I hope to solve is that a Maintainer can stage changes in
> any branch in the contrib repos making it difficult for folks to track
> their back port requests. The also makes it harder to automate any kind
> of build automation.
> 
> I would like to propose a contrib naming scheme for the stable release
> branches. I am thinking of the following:
> 
> stable/{version}-next or {special char}_stable/{version}-next.
> 
>    "version" is either the code name or numeric like in bitbake.
> 
>    "special char" would be used to have these branches at the top of th
> list, if we wont that.

I like this branch unification!

I know we discussed this at OEDEM and there was some convenience reason given, 
but can we also standardize on the tree? I.e. openembedded-core-contrib vs. 
poky-contrib?


> We can apply this to all OE / Yocto repos that have stable branch
> maintenance process.
> 
> If we standardize on a naming scheme, We can then document this so
> contributers can monitor their requests more easily. The community can
> see what changes are being backport.  This will enable the possibility
> to automate builds, etc. 
> 
> let me know what you think.
> 
> Kind regards,
> 
> Armin
> 
> 
> 
> _______________________________________________
> Openembedded-architecture mailing list
> Openembedded-architecture at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-architecture