Versioning Changes - Githubissues

OpenVoiceOS / ovos-technical-manual

developer oriented documentation

https://openvoiceos.github.io/ovos-technical-manual

Creative Commons Zero v1.0 Universal

4 stars 8 forks source link

Versioning Changes #17

Open NeonDaniel opened 7 months ago

NeonDaniel commented 7 months ago

Current doc: https://github.com/OpenVoiceOS/ovos-technical-manual/blob/master/docs/versioning.md

I would propose we follow the Python spec and use dev for the alpha channel and a or b for the beta channel (a is consistent with what we have been doing, I think b would be more logical).

This also makes sense that dev releases follow the dev branch. Open to input but I think we do need some release versioning that identifies releases from the testing branch differently than the dev branch.

builderjer commented 7 months ago

With this, I think we need a good contributions guide. Things that must be there in order for a PR to be looked at. Something for users that want to contribute.

NeonDaniel commented 7 months ago

Possibly an integration guide as well. To summarize some conversation on Matrix regarding the current implementation:

Integrators can pin the testing branch for validation
Mixing pre-release identifiers is discouraged per the linked Python spec, so differentiating dev from testing with version strings is not as simple as my initial proposal
In most cases, the code on the testing branch will correspond to a specific alpha release