Isn't that the equivalent of people generally doing sudo apt-get dist-upgrade vs those on the bleeding edge doing sudo rpi-update?DougieLawson wrote:Perhaps the answer is to only ever publish the "bleeding egde" untested stuff on BRANCH=next and only have camera code and fully tested kernel/bootcode/"firmware" stuff on the master branch. That way I have to do something special to attempt to render my RPi as a non-bootable zombie.
It's even documented that way at http://www.raspberrypi.org/documentatio ... pdating.md
So you've already been warned that rpi-update is giving you the bleeding edge which has had less testing.Updating the kernel and firmware
The kernel and firmware are installed as a Debian package, and so will also get updates when using the procedure above. These packages are updated infrequently (after extensive testing); if you want to try more recent experimental software, it's also easy to update to the latest available version using the rpi-update tool.
Perhaps someone who actually has to maintain these things would care to comment (though this is a slightly hidden discussion given the thread title), but otherwise I'm dropping out as I have no direct input on releasing.