You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of this writing, unpythonic has been around for approximately three years, and has in effect adhered to the minor/major version bumping conventions of semantic versioning for two years of that; beginning with 0.14.0, released 18 March 2019.
However, due to the leading zero, we do not currently follow the semver spec to the letter. This defeats the purpose of following the semver conventions, so we should definitely fix this.
Therefore, now that the long-in-development 0.15.0 is done, there will never be a version numbered 0.16.0. Instead, we will officially exit the 0.x.y phase of development, and release 1.0.0.
The final content of the 1.0.0 release has not been decided yet. What I can say at this point is that it will be either:
The next batch of breaking changes, that would logically be "0.16.0", because doing that requires a major version bump anyway.
OR:
A rebrand of 0.15.x, for some convenient value of x, to advertise the already-present 1.0.0-ness of the codebase as early as possible. This could possibly be even 0.15.0, after it has sat on PyPI for a while; this depends on when I take on the development of the next batch of features.
As of this writing,
unpythonic
has been around for approximately three years, and has in effect adhered to the minor/major version bumping conventions of semantic versioning for two years of that; beginning with 0.14.0, released 18 March 2019.However, due to the leading zero, we do not currently follow the semver spec to the letter. This defeats the purpose of following the semver conventions, so we should definitely fix this.
Therefore, now that the long-in-development 0.15.0 is done, there will never be a version numbered 0.16.0. Instead, we will officially exit the 0.x.y phase of development, and release 1.0.0.
The final content of the 1.0.0 release has not been decided yet. What I can say at this point is that it will be either:
OR:
Releasing an official 1.0.0 should finally get us a blue shields.io PyPI version badge. See the source code in
version.js
andcolor-formatters.js
- it's the leading zero that's making the badge orange.The text was updated successfully, but these errors were encountered: