Adding a <dev> branch as pre-release

biomedicalinformaticsgroup / Sargasso

Sargasso disambiguates mixed-species high-throughput sequencing data.

http://biomedicalinformaticsgroup.github.io/Sargasso/

Other

8 stars 4 forks source link

Adding a <dev> branch as pre-release #70

Closed hxin closed 6 years ago

hxin commented 6 years ago

I was fixing #69 when I realized that we might need a dev/pre-release branch to avoid committing everything to master once they are ready. The branch should be used where we commit the changes until they are enough for a new release. Only the dev branch can be merged into master so that the dev will always be ahead of master. This also keeps the 'release' clean. What do you think?@lweasel

hxin commented 6 years ago

This also keeps the master/release consistency, so when user install Sargasso with: pip install git+https://github.com/statbio/Sargasso.git They are installing the version in the release note, rather than some version ahead of the release.

lweasel commented 6 years ago

Yes, makes complete sense going forward from now - let's do this.

hxin commented 6 years ago

dev was created.