Semantic versioning of MKPs

What is with situations where we have to backport a change to a package that has to be compatible with 2.0 or even 1.6?
There are a number of small incompatabilities between 2.1 and 2.0 that have to be tracked.