+1. Another methodology would be: only update when a Major revision comes and in that case update to the PREVIOUS release's final version. Example: say the 18s go up to 18.15 then 19.0 comes: you update to 18.15 because presumably that was a highly stable final 18 series release prior to a shift and flurry of point releases that follow a major update. Then, when 20 drops, you roll to 19.xx final. In that scenario you are still following development but only adopting highly stable releases whose tonal changes relative to the previous series have been hashed out ad naseum by early adopters.
Bottom line is that the only update that won't affect ANYTHING is the update you don't apply. The point of an update it is to change things. If you don't want to change stuff, don't update.
I'm the first of 100 reply-ers who wiil respond like this: "Just update once every 3 months". Problem solved.
To the OP, you're never going to win this argument. The bedroom fanboys out weigh you 100:1.
As I've said when this has come up previously, touring acts are not taking risks by updating constantly.
It has nothing to do with "bedroom fanboys". You may be a little disenfranchised with the brand, but antagonizing a bunch of paying customers for loving the brand adds nothing to your post. As you said, touring acts are not taking the risks by updating constantly. Bottom line, he won't win the argument - not because he's outnumbered by loyal fans, but because what he's saying is "please don't give us any more updates, because I don't want them, and yet somehow I can't control myself and end up uploading them to my unit".
Thats not what the OP ment. In my understanding he said: Whats the benfit of 1 quick bug fix, if you create 10+ new bugs caused by a way too quick bug fix release.
Thats not what the OP ment. In my understanding he said: Whats the benfit of 1 quick bug fix, if you create 10+ new bugs caused by a way too quick bug fix release.
Show me a case where this is happened? You can't.