Skip to content
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.

Sign up for GitHub

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

Jump to bottom

New Versioning Scheme #62

Open
shibumi opened this issue Aug 13, 2023 · 1 comment
Open

New Versioning Scheme #62

shibumi opened this issue Aug 13, 2023 · 1 comment
Assignees
@sschuberth @pombredanne @shibumi
Labels
enhancement

Comments

@shibumi
Copy link
Collaborator

shibumi commented Aug 13, 2023 •
edited
Loading

Currently, our README.md defines the following versioning scheme:

The versions will follow the spec. So if the spec is released at 1.0. 
Then all versions in the 1.x.y will follow the 1.x spec.

In #57 we realized how impractical this is, hence I thought about releasing a v1.0.0 and creating a v1.1.0 release after merging the aforementioned PR.

Also, I thought about dropping this version scheme in general and instead we could go with version directories: v1/ or v2/, like some other APIs do.

WDYT? @pombredanne @sschuberth
@shibumi
Copy link
Collaborator Author

shibumi commented Aug 13, 2023

Oh never mind.. while writing this, I realized the README.md actually mentions v1.x.y already 🤔 not sure what I thought.

How far away are we from spec -> v1.0?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sschuberth sschuberth

@pombredanne pombredanne

@shibumi shibumi

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sschuberth @pombredanne @shibumi