bjtheone wrote:Having been on the maintenance side of the equation, building and testing releases and ensuring all is well takes a very real amount of time and resources. Plus the more often you do it, the more likely that you will end up putting out a broken release, as you have less time of soak testing.
So when the newbie family opens up their brand new pi, installs the os, waits around for the update as automated & suggested, then they are going to possibly have a broken system? That hardly seems normal or acceptable. should the update say --WARNING your new system may fail to operate properly after this step?
Presently, no such warning is provided.
Having been on the maintenance side of the equation, building and testing releases and ensuring all is well takes a very real amount of time and resources.
...that needs done, regardless.
You have to look at it from the view of someone who's only experience with the pi
is what has transpired during the prior 15 minutes. You tell them now system is searching for updates & will install them, ok?
With no warning about potential problems, who is going to say no?