At the moment we rely on individual layers having a branch that matches the name of the release branch (e.g. fido) for it to show up as being compatible with a particular release; however that doesn't always match reality; e.g. meta-angstrom has branch names that correspond with its releases. We have the ability to map branch names in the database but this is not exposed in the UI.
isn't this done?
No, it isn't. You still have to be an admin to be able to see/change this through the admin interface.
think this if fixed via http://git.yoctoproject.org/cgit/cgit.cgi/layerindex-web/commit/?id=8501a6da40e733fcbda5d23d3f70628bb005d6ff
Not yet fixed.
The actual_branch field is only available in the admin UI. We need to expose this to the layer maintainer UI such that a layer can be edited and a specific Branch can be mapped to the actual_branch for the LayerBranch object. e.g. if a layer has a kirkstone-1.2.3 versioned branch, the layer maintainer should be able to set actual_branch=kirkstone-1.2.3 for the meta-layer:kirkstone LayerBranch object. Some layers have multiple branches which are compatible with a given release. This is out of scope for the design of layerindex-web. Only one layer will be mapped to one branch (only one unique LayerBranch object). It is up to the layer maintainer to decide which one they prefer to be mapped. If a product wants versioned layers, it should create new Layer objects with the version in the name.
https://patchwork.yoctoproject.org/project/yocto/patch/083c23476450ea85e7d3f4a4aff4bb619c7b59fb.1703911977.git.tim.orling@konsulko.com/ There may be additional behavior that needs to be added after this has been in use for a while, but most likely that will be tracked in new bugs.
Merged in: https://git.yoctoproject.org/layerindex-web/commit/?id=b361715cc43a0939a577f126dfb7276ee6b956be and enhanced in: https://git.yoctoproject.org/layerindex-web/commit/?id=b0af957ac734b76bc7cc2b45b0beb1cde74df0a6 meta-qt6 is an example of a layer that exposes this.