[Suggestion] Freeze U-boot packages on working versions
Lately we have had a slew of issues regarding u-boot.
We shouldn't expect regressions like that in upstream u-boot, but that has happened a lot lately.
So I will now suggest that when we find a u-boot package for a device, which works, it does not get touched/upgraded unless the update has been thoroughly tested.
I know I'm guilty of updating uboot packages, when it's not really needed. And users blindly reflash uboot even though they have no idea what it actually does.
So I would like some opinions on this. @appelgriebsch @spikerguy @darksky.
After next stable update, I will spend some time checking some u-boots on devices that I still use u-boot on, like Rock Pi 4B, Orange Pi 3 and 4 LTS, Odroid C4 and so on, just to make sure they still work. I won't be testing Pinebook, Pinebook Pro and Odroid N2+ as I use Tow-Boot on these, or the RockPro64 I have as that's in production.
We should maybe even try working towards not even providing packages for u-boot in the future and just have the tools and installer download and flash u-boot binaries we know work, from our gitlab repo. That way there's nothing for users to flash and therefore nothing for them to mess up.
I've placed this issue in the uboot-pinebookpro repo, but it's about all the u-boot packages.