|
I'm not really understanding what the issue is here to spark all this discussion, but my personal approach as an official author/maintainer is to just make sure I use a number higher than whatever else is out there on the thread in the rare circumstances this happens.
If my last official release is x.y.9 and someone posted an unofficial x.y.10 build on the thread then I would just make my next version x.y.11. Does that mean a gap in the release notes number sequence - sure, but it doesn't matter in the slightest. Would an x.y.9.1 build number by them be a cleaner option - sure, but I'm not going to jump all over someone for using x.y.10 instead. These circumstances (on my plugins at least) are so incredibly rare where someone is posting another build on one of my threads that it's just not worth debating imo.
In my day job - absolutely I have very strict approaches, stick to semantic versioning with major.minor.build.revision etc. But for plugins I am way more casual about it - 0 or 1 for the first number to indicate a not yet released alpha of new plugins vs a released one, the second digit for major feature releases/rewrites such as python version changes, and the third digit for bug fixes/minor new features. Would the sky fall in if I broke my own "rules" just to make sure my next official build has a bigger number than an unofficial one on a thread? No.
|