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.

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

Open
K-Meech opened this issue Feb 18, 2022 · 6 comments
Open

Versioning #71

K-Meech opened this issue Feb 18, 2022 · 6 comments

Comments

@K-Meech
Copy link
Contributor

K-Meech commented Feb 18, 2022

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).

@constantinpape
Copy link
Contributor

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 0.2.0 and I think we are (almost?) ready for it: I had a list of things to do for the new spec in #5 and almost all of this is done (so I closed the issue).
Here are the last remaining two points from #5 and one more relevant issue:

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.

@K-Meech
Copy link
Contributor Author

K-Meech commented Feb 18, 2022

This sounds good to me! I don't think there's much reason to version the markdown.

@constantinpape
Copy link
Contributor

#57 is resolved now and that was the last thing I wanted to do before releasing the 0.2. spec.
Anything missing from your side, @tischi, @K-Meech? Otherwise I will make the github release tomorrow.

@tischi
Copy link
Contributor

tischi commented Feb 24, 2022

Fine with me to release.

@K-Meech
Copy link
Contributor Author

K-Meech commented Feb 24, 2022

Sounds good - go ahead!

@constantinpape
Copy link
Contributor

Done! I will still leave this issue open to keep track fo the two non-release related TODOs I copied here.

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

3 participants