Firmware Release Process

[Sim-plicity Dev]

At the time of writing, we have 13 different hardware configurations/wheelbases that we develop firmware for. We expect this number to be in excess of 25 by the end of 2021 and approach 40 by the end of 2022.

To help manage the complexity of distributing firmware across these multiple configurations, we are rolling out an automated release mechanism utilizing Github repositories.

There will be Alpha, Beta & Stable repositories each with individual releases consisting of the firmware & software installers for each configuration.

All firmware will now be versioned in the vYY.MM.xx format.
YY: 2 digit year when development started
MM: 2 digit month when development started
xx: 2 digit version number incremented for each release

This differs from the previous versioning according to release month.

Each release will start in the Alpha repository (barely usable) progressing through Beta while being refined, then promoted to Stable once all identified issues are resolved.

Once a release is promoted, a new release is either promoted from a lower repository or created to take its place.
This means, eventually there will be 3 active releases for every configuration

• Alpha for the adventurous
• Beta for those who need the new features & would like to help in identifying and resolving issues
• Stable for those who just want to drive

To begin the process, we've created the v21.02.05 release in Alpha. This is a significantly more polished version than will be the case for Alpha in future & should quickly be promoted to Beta.

We encourage you to download & install the appropriate installer at the stage you feel most comfortable and discuss your thoughts & issues in the "v21.02.05 Discussion Thread"

Regards
Sim-plicity Development Team