Description
The current master
branch was used for both development and releases in prior work on CodeMeta. I propose that we have an urgent need to use a GitFlow style process so that changes targeting the next release are done on a develop
branch, which is then only merged to master upon release. This would allow the current master
view on GitHub to always reflect the current stable release, but let work on the next version continue on develop
.
I propose that we follow a system like the one we developed for science on schema.org. Feedback appreciated... cc: @cboettig @amoeba
We might even consider merging CodeMeta into Science on Schema.org given that they have a mature community working towards similar goals on the Dataset side of schema.org. Feedback @cboettig @ashepherd ?