Changes in branches management

[JF002]

The @InfiniTimeOrg/core-developers noticed that the branch management is not optimal right now. InfiniTime is currently based on 2 'main' branches : master and develop. We create new branches from develop and merge develop in master to release a new official version of InfiniTime.

This workflow gives us the opportunity to release hotfixes from master while still working on other changes in develop.

However, this workflow based on 2 branches brings a bit of complexity (especially when releasing a new version of InfiniTime) which we don't need. That's why we decided to switch to a single "main" branch model.

To make the change more explicit, we decided that the new "main" branch will be called main (instead of develop and master). All PR will have to be merged in main and releases will be tagged directly on main as well. We'll still have the opportunity to create support branch in case we need to patch previous release.

What does it change for you developers and contributor? Since we are renaming develop to main, Github will automatically redirect all links pointing to the old develop to the new main. However, you'll probably need to update your working copy as explained here : https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch#updating-a-local-clone-after-a-branch-name-changes.

Github should also notify you about this change like below :