8432 2015-10-02 01:31:09 +0000 align release versioning scheme with OE-Core 2016-04-22 14:36:31 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake unspecified All Multiple RESOLVED WONTFIX Medium enhancement 2.1 1 raj.khem richard.purdie otavio poky.bs.watcher poky.watcher --- --- Yes (doc changes required) oldest_to_newest 54919 0 raj.khem 2015-10-02 01:31:09 +0000 We do not have consistent release numbering across OE components. This tracker is for discussing and fixing that in 2.1 release. Secondly there is codename which is used for branching the releases but there is no obvious relation between release numbers and the branch name. This could be consolidated to have consistent naming across all release components. It would only make sense if we were to release the components independently with there own life cycle but there seems to be not the case. 54920 1 raj.khem 2015-10-02 01:34:45 +0000 it would be nice that yocto project reference distro also used same release naming convention as rest of components and drop any codenames in use. The distro should be renamed to reflect it being a reference distro, its not clear to user the obvious relation between poky and yocto project and reference distro. The heterogenous naming just makes it worse. 61561 2 richard.purdie 2016-04-22 14:36:31 +0000 Having given this a lot of thought, I believe the branch codenames are the only real way to make the OE ecosystem work. This is because lots of different pieces have versions and we need something different to all things to match clearly. I'm therefore not planning to change the use of codenames. We are slowly removing confusing numbers like the poky version numbers where we can.