rootstrap
Sync development and master
Given we released our first complete version, i decided to sync development with master. From now, we must work from development branch and only update master when we are going to release a new version.
I'm not sure this is a common approach for open sourced gems. The usual way to develop/maintain I've seen is:
- Anyone (including the maintainers) create a PR to introduce a feature/fix
- The PR (once approved by reviewers and the CI) gets merged into master
- Every so often (once a day, twice a week, once a week, once a month, ... whatever works best for us) one of the maintainers release a new version of the gem
The release implies updating the semver string in the gem, creating the tag/release in github, building the gem and lastly pushing the gem to rubygems (more info about releasing here)
In general by having only one main branch (master) will make it easier for anyone to jump in, clone the project and branch off from there. On the contrary, introducing a development branch will only create one more step, or better said one more "bus stop", where all contributions will remain there, until merged to master. At the end, the development branch might not be entirely necessary.
Offtopic: Have you considered on adding a changelog file? Or are the changes mentioned in every release?
