Comments by "" (@grokitall) on "It's time to fix semantic versioning" video.

  1. You can still do that. The thing theo was referring to was that not having known about the special case of 0.minor.patch having minor be both the api breaking and api non breaking, he now cannot go back and take advantage of it now he does know about it. If you want to continue maintaining version 2 code after moving to version 3, this is no problem, you just cannot add api breaking changes to it. And yes, global state variables having the default changed is an api change, it is just a very bad way of defining the api.
    2
  2. ​ @kayakMike1000 this is exactly what the rust maintainer who just quit suggested, with them doing the maintenance, but the c maintainer tried insisting that the code was not in his part of the kernel tree, hence suggesting getting others involved to resolve the impasse. You need consistent project wide rules saying what goes where, which we do not have yet for the kernel.
    1
  3. No cognitive load, except for the fact that it stripes all the information contained in the semantic versioning.
    1