Improve release cycle

[meier-rene]

Here are the notes and to does from our webmeeting with @laurentheirendt

• make a dev branch
• improve contribution guidelines (checkout the dev branch, ...)
• push / merge against the dev branch
• merge with master when all tests succeed
• ARTENOLIS could be an alternative to Jenkins CI: https://arxiv.org/pdf/1712.05236.pdf https://prince.lcsb.uni.lu/jenkins/
• hands on:
  • create branch dev and push to it
  • GitHub Branch properties for master, dev: require status checks to pass before merging; include administrators
  • Open pull request > edit > branch is changeable; pass tests; merge
  • tag the 'merge into master' with a release version and comments of the changes

[laurentheirendt]

cc: @Trefex, @schymane

[Trefex]

Technically Artenolis is Jenkins, I guess @meier-rene meant that it could be an alternative to current TravisCI?

[schymane]

I assumed the same thing ;-)

[tsufz]

I think, we need to commit a policy for release frequency. I suggest to daily or latest weekly. I think it is an important pull factor for contributors to see their submitted records online ASAP. It is also important to replace fixed records ASAP with respect to warranty requirements. At least massbank,eu is bound to German law at that point. I will set the repository at MassBank.eu to dev until we have a commitment and solution for the release process.