That tends to be the biggest cop out excuse for libraries. Just do a major version release. The fact this library lies about the encodingis extremely problematic and causes numerous bugs. Any program currently using this library is already incorrect because of this behavior. Actually exposing the problem makes it easier for people to fix.
in reply to subject of https://hyp.is/VeTJlpN0Ee2mNKOVyQ-B5g/github.com/mikel/mail/issues/902
Agree, but we're stuck with API compatibility for a good while.
Faatu aj na laytanam.
Faatu a placé sa calebasse en haut.
faatu -- a feminine name of Arabic origin. 👩🏽
aj v. -- place on top 🔝, perch.
na -- her (?).
laytan+am (laytan) gi -- small calabash (to have).
I'm still calling this v1.00 as this is what will be included in the first print run.
There seems to be an artificial pressure and a false assumption that the version that gets printed and included in the box be the "magic number" 1.00.
But I think there is absolutely nothing bad or to be ashamed of to have the version number printed in the rule book be 1.47 or even 2.0. (Or, of course, you could just not print it at all.) It's just being transparent/honest about how many versions/revisions you've made.