Philosophy around Branches and Releases

While versioning have been kind of chaotic it has somewhat fallen into a somewhat predictable pattern.

Branches:

nightly

These pushes are the very bleeding edge. If anything works here, it won't stay that way for long, as I use this to push code to the repo and then pull it into my prototype rig. Only look here out of curiosity of what I am working on at the moment.

main

When I have a new version of the codebase that seems to work in the nightly branch, I'll merge it into main. Mind you, I may have overlooked something hidden. All I can say when it's merged to here, is that it seems to not fall apart at first glance.

Releases

When things seem to be stable enough to be given a version number, it gets to two stages.

Prerelease

These are basically Beta versions. All seems well, and I want to have a easily findable snapshot of what the current thing is. And it stays in prerelease mode until I actually do a full redeployment.

Stable Release

These don't only look like they work. But they also have survived my full redeployment routine. Meaning, I flash the Pi's boot drive to stock Raspberry Pi OS Lite and do a full from scratch installation of the VOP. This is the only version I would say is close to actually stable for use in a production. But I am so far only one person doing everything, so edge cases may remain and I want to know about them. So if you find anything. Tell me through the issue tracker!