Release 2.1.0

[jwalgran]

• Start a new release branch:

$ git flow release start 2.1.0

• Rotate CHANGELOG.md (following Keep a Changelog principles)
• Ensure outstanding changes are committed:

$ git status # Is the git staging area clean?
$ git add CHANGELOG.md
$ git commit -m "2.1.0"

• Publish the release branch:

$ git flow release publish 2.1.0

• Test the release branch on staging
• Start a new release pipeline job with the SHA (see command below) of release/2.1.0 that was tested on staging

$ git rev-parse --short HEAD

• Run migrations, if applicable (see the showmigrations release pipeline stage):

$ ./scripts/manage.py ecsmanage -e production migrate

• Finish and publish the release branch:
  • When prompted, keep default commit messages
  • Use 2.1.0 as the tag message

$ git flow release finish -p 2.1.0