Release 3.0.0

[thinkh]

Release notes

• Use POST method for heatmap loading if URL is too long Use POST method for heatmap loading if URL is too long #70
• General repo changes General repo changes #71
• Fix Typescript error in force_directed_graph.ts Fix Typescript error in force_directed_graph.ts #74
• Update node-sass to ^4.12.0 Update node-sass to ^4.12.0 #75
• Add TS compiler flags for i18n to tsconfig.json Add TS compiler flags for i18n to tsconfig.json #76
• Update project config + CI configs with Node 12 Update project config + CI configs with Node 12 #73

Checklists

Release preparation

• Create new release-x.x.x branch (based on develop branch)
• Collect changes and write release notes
• Draft release PR in GitHub that merges the release-x.x.x into the master branch

Release dependencies first

In case of dependent Phovea/TDP repositories follow dependency tree from the top:

• Release dependent repositories if they contain changes first before proceeding here
• Replace git dependencies in package.json with new version range (e.g., "phovea_core": "^2.3.1")
• Commit and push new dependencies
• Wait until build is successful
• Repeat with other repositories/dependencies or proceed with next section

Update version

• Check version numbers of dependencies again
• Check if build is successful
• Update this version number following semver
• Run npm install on release branch to update package-lock.json
• Commit and push package.json and package-lock.json with new version number
• Wait until build is successful
• Assign reviewer and wait for final review
• Merge this pull request into master branch

Publish npm release

The steps of this section are only necessary if the code is public and should be published to the npm registry.

• npm run build to build the bundles
• npm login caleydo-bot
• npm publish
• Check release on npmjs.com

Create GitHub release

• Draft a new release (Code -> Releases -> Draft a new release)
• Use new version number as tag (e.g., v2.3.1)
• Copy release notes
• Publish release

Prepeare next develop release

• Switch to develop branch
• Update version in package.json and package-lock.json to <next patch version>-SNAPSHOT (e.g., 2.3.1 to 2.3.2-SNAPSHOT)
• Revert dependencies in package.json to develop branches (e.g., "phovea_core": "github:phovea/phovea_core#develop")
• Revert dependencies in requirements.txt to develop branches (e.g., -e git+https://github.com/phovea/phovea_server.git@develop#egg=phovea_server)
• Commit and push changes

🏁 Finish line

• Inform colleagues and customers about the release
• Celebrate the new release 🥳