Expanding a bit: the plan is that 2.0 just switches us to a new versioning system. The tl;dr is: Versions start going 2.0, 2.1, 2.2, then 3.0, 3.1, 3.2, then 4

Expanding a bit: the plan is that 2.0 just switches us to a new versioning system. The tl;dr is: Versions start going 2.0, 2.1, 2.2, then 3.0, 3.1, 3.2, then 4.0, 4.1, etc. Every X.2 is a long-term support release. The deprecation cycle gets tweaked so that if you're on, say, 2.2 LTS and your codebase runs with no deprecation warnings, then you'll be able to just run as-is on 3.2 LTS. You can then clean up any deprecation warnings on 3.2, and you'd be good to go for 4.2 LTS, etc.