Skip to content

Semantic Versioning for Major version zero (0.y.z) #175

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
pschroen opened this issue Aug 2, 2023 · 1 comment
Closed

Semantic Versioning for Major version zero (0.y.z) #175

pschroen opened this issue Aug 2, 2023 · 1 comment

Comments

@pschroen
Copy link
Contributor

pschroen commented Aug 2, 2023

A proposal for moving to the same semantic versioning as three.js, this has been a hot topic over the years, however the three.js maintainers are sticking with the Major version zero (0.y.z) convention as it's specifically meant for development with potentially breaking changes of each release.

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

I should also point-out the core features and functionality haven't really changed much with OGL, compared to three.js which (especially this year) really does have breaking changes with each release. 😅

All of this to say, maybe it's time to remove the alpha note in the readme, imho this library is very stable in comparison, and warrants removing the notice and switching to at-least "Major version zero (0.y.z)", with breaking changes inferred. 😉

Let me know what you think!

References:

@gordonnl
Copy link
Contributor

gordonnl commented Aug 2, 2023

Sure, let's do 1.0.0! Thanks for the input and reference.

@gordonnl gordonnl closed this as completed Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants