Automate the release process #388
Labels
2 - pick next
Used to mark issues which are next up in the queue to be worked on. The tag is non-binding
3 - in progress
Someone is working on this ticket
Milestone
I'll try to follow some suggestions from http://timperrett.com/2016/10/02/continuous-delivery-for-scala-with-travisci/. The idea is this:
release
branchNote: if we don't follow the
release
branch approach, we need to make sure that the version is bumped up to a snapshot version after a release.The text was updated successfully, but these errors were encountered: