With the point of view provided by @stas, I stand corrected. Semantic versioning will not help.
E.g. true that 1.x1.y1 -> 2.x2.y2 conveys breaking changes and therefore the consumer will be extra aware - which was the point of me filing 1739. E.g. Finding Image*List nuked between patch versions was a rather rude shock for me.
However given that we want to rapidly iterate - even if we agree to follow semantic versioning - every new release will have breaking changes.
And even if there is 1 breaking change per release, instead of 1.0.46 -> 1.0.47, we will have 46.0.0 -> 47.0.0.
Which doesn’t help at all. Unless we following release-branching-backporting process - which will require non trivial amounts resources.
Given that fastai lib is not ‘go-live’ at the scale of keras/tf/etc - that amount of resources has no ROI.