Unstable branch

[glennvl]

Summary

Updates are done from master, there are no officiel releases. This is not something we can easily change because it would be a breaking change that affects all end users. So that ship has sailed.

Problem: Large changes that ideally require more testing are immediately pushed to all end users.

Solution: What we can do is find an alternative way of improving release management. This PR adds an unstable branch. The end user can then decide to opt in to the unstable branch.

Usage of the unstable branch

• Merge large changes to the unstable branch first instead of immediately to master
• End users who opt in to the unstable branch can test the changes
• End users who don't opt in to the unstable branch keep using the stable version on master
• The unstable branch has to be rebased on master each time a change is made to master
• Example: Update to latest wine version

Usage of the master branch

• Smaller changes and bug fixes can immediately be pushed to master
• When changes in the unstable branch are considered stable, push them to master

Implementation

• Update github workflows to build both a latest and unstable image
• Add an ENABLE_UNSTABLE configuration option to allow the end user to opt into the unstable branch

Todo

• Test github workflows