Quote:
Originally Posted by IanD
Not to mention the (presumably) large number of people who haven't upgraded to this version yet. Some of us are still on 3.15.0, and patiently waiting* for our local affiliate to catch up.
* Yes, I know I can update anyway, but the point is that most people won't know how, or even care - until their device eventually updates itself, and then (maybe) start getting problems. Personally, I'm happy with 3.15.0 and haven't seen anything critical that would persuade me to upgrade ... and this bug is a good reason not to bother.
|
But this bug (as you call it) can be patched away in two different ways. You know where to find the patches and you know you can update to 3.17.0 without getting caught by sickle.