Create a release committee for Mongolid

[vidalvasconcelos]

Proposal

We currently have no governance model for this project I propose that we create a contribution committee that will be responsible for organizing the releases and curating the issues and contributions to this project.

Release workflow

The first step is to formalize the workflow of a release that currently does not exist and has made life difficult for those who need or want to contribute to this project, Initially we can adopt a pattern with the one established in the laravel repository with the release branches active in the repository like:

• v0.8 (not supported)
• v2.x (current version)
• v3.x (next version)
• main (development branch)

These tasks will cause problems in the local setup of those who are currently contributing but should be resolved with a few changes, like:

Moving to master to v3.x:

git branch -m v3 v3.x
git fetch origin
git branch -u origin/v3.x v3.x
git remote set-head origin -a