Release branches instead of tags

[StaticRocket]

Currently there are asynchronous updates to documentation, often occurring days or weeks after a release. In addition to this, Applications Engineers often need to update documents relevant to their release post arago tags and include known issues and workarounds.

As a result I would like to move to a release branch scheme, where each major version tag (currently tracked in device version.txt files) receives it's own branch from main for relevant updates. Only devices who's version.txt corresponds to the branch name should be prioritized on these branches.

CICD and release previews will still only process on the master branch, but any postmortem updates can at least be tracked and associated with the correct release directly.

Does this sound reasonable?

[bryanbrattlof]

Yes that sounds reasonable. Being able to fix typos in old docs or add links to software fixes would make this worth the complication the multi-branch integration scheme adds.

[StaticRocket]

Naturally, Github will only build and deploy master builds due to deployment size constraints and general workflow shenanigans.