-
Notifications
You must be signed in to change notification settings - Fork 3
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
Versioning #71
Comments
My plan would be to only make a new release for actual changes in the spec (as defined by the jsonschema). I don't think that we need to version the markdown, mobie.github.io is be rendered from master anyways. Or do you see any reason to version based on changes in the markdown, @tischi @K-Meech? The first release would then be
None of this is really blocking us from making the release, so if there is a good reason we could also make the release right now. |
This sounds good to me! I don't think there's much reason to version the markdown. |
Fine with me to release. |
Sounds good - go ahead! |
Done! I will still leave this issue open to keep track fo the two non-release related TODOs I copied here. |
How should we define releases for this repo?
From this pr: #70
We should define what exactly a release here means, as it makes most sense to use it to keep track of changes in the sepc (as defined by the jsonschema)
My initial thought was to create a 0.2.0 once the current spec is fixed (which I think is the case now).
The text was updated successfully, but these errors were encountered: