📣 Announcement: Update to branching strategy

[garrytrinder]

In response to #1545, we will be making a change to our branching strategy to support this.

As of the next release cycle, we will be discontinuing the dev branch in favour of a single branch strategy.

We currently use a traditional master and dev strategy to provide separation between our monthly stable release code and weekly beta release code.

Whilst this model has served us well, we feel that using the dev branch is no longer required and that moving to a single branch strategy, we reduce the effort of managing code merges between multiple branches.

As we already employ quality gates such as automated builds and tests as part of our continuous integration process, peer review of pull requests and have small batch sizes, we can merge code directly to master with confidence, ensuring that our quality remains high.

This change will enable us to merge code more frequently resulting in faster integration of new features, updates and fixes to better serve the community that uses the CLI.

We will also be updating our documentation to reflect this change to help support you. Don't hesitate to let us know if you have any feedback.

Waldek, Velin, Garry and Appie

[waldekmastykarz]

The new branching strategy is in place