Versioning

[TheBakedPotato]

A common strategy for versioning software through version control software is to use tagged commits on say the main branch and those are the definite versions released. How we determine what makes a version, or when a new version has been released, is obviously up for discussion. However, a version only increases when it's agreed upon that the code is stable, not blocking bugs, and then it is released.

GitHub does have some wonderful tools to do releases. I created a little test repo for myself here to try out making releases and stuff. It's only quite slick and will hopefully make it clear to others viewing the repo what version is the latest and allow them to easily download the source code for past versions.

If you view that repo, in the UI where you can select branches, you can also view tags. Currently there is one tag, v0.0.1, just for demonstration purposes but it does help showcase the utility of the tag and release feature of a git repo on GitHub. Making the release and creating the tag on the commit do not require any more advanced knowledge of git. It is simply all done through the GitHub UI.

[ForrestErickson]

Excellent initiative.

I will make two feature requests with which to practice.

Unfortunately because I do not fully understand the possibilities I have to start with what I am guessing is a wrong approach.
And I will do so with Arduino like code to run on an UNO.

@ForrestErickson

[ForrestErickson]

There are now issues at: https://github.com/TheBakedPotato/test-repository/issues

[TheBakedPotato]

Cool, thank you! Yes, I will make my test repo compile on the ESP32-WR00M so others on the team can try it out. I will try to get some versioning or something underway so we can test it and see if the workflow makes sense for Krake