OpenPLi in its wisdom has frozen the plugin on an old version. That means the .xml files can no longer be downloaded and then when there is a provider update the plugin gets a bad name for not working properly when the real problem is the code freeze imposed beyond the control of the plugin authors.
I am getting EXTREMELY tired about this Huevos! I seem to have to repeat myself all the time.
We have not decided to freeze anything. Release builds are stable and final builds, they are not nightly updated. So even if they had AUTOREV, users would not get a new version of the plugin! Every now and then we run a hotfix build, and we bump the SRCREV's, also for this plugin.
My point remains: users that, for whatever reason, can not update the plugin are left behind by your design choice. Your design blocks the download of the xml's, because you can't be bothered to deal with backward compatibility for your users. This is not the problem or the fault of the image builder, it is a shortcoming in the product.
It is time to stop blaming other people for your poor design choices!
edit: There is however an issue that the SRCREV only seems to be updated in the e2openplugins recipe, which we don't use. I've corrected that.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.