3 ms·
The author makes it sound like the developers won't care about the bug because the user waited from 4.4 until 5.6 to upgrade. In this case the user is better o
by LukeB_UK 12y ago
The author makes it sound like the developers won't care about the bug because the user waited from 4.4 until 5.6 to upgrade.
In this case the user is better off not upgrading if the developers aren't doing to do anything about it.
- sarciszewski 12y agoNo, in this case, the user should have been upgrading this whole time, not putting it off for 3+ years. Downvote me all you want. Tough love is what's needed here. Hiding my comments isn't going to make peoples' negligence any less their fault.
- obsurveyor 12y agoTheir network card still would have broken at some point and they'd be in the same bind they are in now: A non-working critical part and at the mercy of the developers to identify and fix the bug.
- ams6110 12y agoExactly this thing happened to me in an OpenBSD upgrade. My network card no longer worked. That prompted me to actually read the release notes, and I quickly found the reason.
- Yen 12y agoThe author didn't say the developers wouldn't care, but that the extra effort means the developers wouldn't care enough. Fixing a bug requires figuring out what's broken, and that's a lot easier when you know something broke between 4.7 and 4.8, than in any of the revisions between 4.4 and 5.6. (Especially if there were actually two latent bugs in 4.4, one of which got exposed in 4.8, and one of which got exposed in 5.2)