New Release logic

[timmwille]

I think it is time to define a better development and release workflow?

Currently we're at 2.0 release but need to update/fix/patch a bunch of documentation details and just added new formatting etc. to it. so we definitly need a Patch logic.

Semantic versioning would mean for example:

1. • Major releases 2.x and so on (when the overall Concept for Content and Packaging changes e.g. the case (so 1.5 is a bit off))
2. • Minor releases 2.1 when generally small changes happen to the hardware (e.g. new parts, small changes to the packaging etc.)
3. • Patches as for 2.1.x to update the official Major and Minor Releases (and documentation) with respective patch-tags

Currently the Tags are named only for Main Releases as ASKotec-2.0 so what would be for the new name convention the best approach when Minor and Patch tags are given?

Only the ASKotec-1.5 tag is a bit off, but was never meant as a full new product, rather a test kit which brings me to the aspect that in the future a lot of variations might happen (complete redesign and also new subject oriented or smaller Kits with more specific easy to understand use-cases in mind as e.g. Community Repair Café or also the ASKriot the ASKsek etc.)

@hoijui @bmen would be great to get your feedback on this.

[timmwille]

https://github.com/B-yine/-ASKriot

https://github.com/ASKnetCommunity/Minimal-Repair-Setup

https://github.com/ASKnetCommunity/ASKsek-Launched-in-Bor-Town

[timmwille]

maybe it is best to exclude the new variants discussion into a new Issue