I believe that putting off a major release such as 2.0 for several years is
an artificial way to prevent ever removing anything that is deprecated.
Following SemVer should be part of a reasonable software release cycle, and
a reasonable software release cycle should involve periodic major releases
Let’s separate the discussion into these parts:
- What does SemVer say and how do we apply it
- When should we remove deprecated code
- Should we remove the admin source code entirely
1) SemVer
Straight from the spec:
> Major version X (X.y.z | X > 0) MUST be incremented if any backwards
> in
I'm not sure if I'm interpreting various parts of this conversation
correctly, but it seems that one view being assumed is that the actual
removal of deprecated APIs *must* happen in the first version of a major
release bump. i.e. for this discussion that would be *2.0.0*. I don't
believe this is a