Changing the development process, branch renaming

[obgm]

@boaks has proposed a new development process which I support. The changes will include renaming the master branch to main.

• In the future, the branch main will contain contributions that have been reviewed by two different team members.
• Releases will be created from tagged versions in the main branch.
• The development branch will contain contributions in an early stage, possibly reviewed by only one team member.

Renaming the default branch will need a slight change on your local working copies as described here. You can do the change at your convenience as for the time being a redirect will be in place.

[obgm]

Update:

• the default branch now is main, and
• the develop HEAD has been merged into main.

[mrdeep1]

Is it worth bumping the version at this point?

[obgm]

Yes, most likely. How about 1.0.0-rc1?

[mrdeep1]

Works for me

[boaks]

Just to mention:
For "develop" I consider, that it will be "reset/force push" from time to time and/or the commits are edited to reflect additional commits from the "main".
For "main" the common grant (no force push, at least not without very good reason).

[obgm]

In most cases, there would be no need for doing a force push on the develop branch either as this is usually done in the PR's source branches only (and --force-with-lease usually removes most of the headache).
Unless the main branch is destroyed, a force push there should never ever be necessary.

[boaks]

I add some instructions to CONTRIBUTING.md, see PR #151.

[boaks]

Done. Created issue #164 and pined that.