constantinpape
commented
2 years ago 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:
- add signing region to source metadata: #57
- CI for static json schema validation (create github actions? https://docs.github.com/en/actions/creating-actions/creating-a-docker-container-action)
- The examples generated by schema-faker don't look very nice (weird names where it needs to match the regexps) and are inconsistent where consistency cannot be enforced through the schema (e.g. sources not matching name). Would be best to write some code around this to choose better names and make things consistent or write the examples manually once we fix the current spec version.
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
tischi
How should we define releases for this repo?
From this pr: https://github.com/mobie/mobie.github.io/pull/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).