The reason is the feedback we got after 10.11.0, which we first raised in January and confirmed in May. A release like 10.11.0 was, by any reasonable measure, a major release - it rewrote the library database - but the version number presented it as a minor update, and people upgraded with expectations to match. The leading 10. never changed and never told anyone anything, so all it did was push the number that actually mattered into the middle position and make “major” releases look minor. Dropping it means the first number moves when the release is big.
lol. All the Jellykins in here lost their minds when this was pointed out.
lol. All the Jellykins in here lost their minds when this was pointed out.