Well the article explicitly mentions the problem we were discussing:
> First, when the above condition ("every new production release is based on
> the previous one") is not satisfied. As an example, take the Python
> programming language. It has two incompatible versions, 2 and 3. Both of them
> receive bugfixes and security patches - however, that doesn't mean a new
> release of Python 3 is based on the commit of the latest release of Python 2.
> The two versions have diverged, and while they surely share a lot of code,
> you can't say that one is based on the other (talking from a purely version
> control perspective).
That is what we like to do though, if not for the upcoming 0.19.2 vs 0.20
split, then later for the v1 vs v2 split, so we might as well figure out how to
do it now.
