Release Camunda Modeler v4.9

[nikku]

Scheduled for 13.07.2021.

What's inside?

See release milestone, changeset v4.8.1...v4.9.0.

• Support Zeebe 1.1 / Camunda Cloud 1.1
• Support bpmn-in-color, connect message flows to call activities
• Improve status bar, show basic what's new communication
• Various other fixes and improvements

Release Checklist

To be done immediately after release date is fixed.

• put up code freeze appointment in calendar (include modeling, qa, infra, and Team-Support)
• inform QA about the release and its details so they can prepare for testing
• put up release appointment in calendar (include modeling, DevRel and Marketing [ Christopher Rogers ])
• add Slack role to release manager (@modeling-release-manager)

To be done after code freeze and prior to the release day to prepare and build the release.

• make sure changes in upstream libraries are merged and released
  • bpmn-js, dmn-js, *-properties-panel, *-moddle, camunda-bpmn-js, form-js, ...
• make sure dependencies to upstream libraries are updated and can be installed (rm -rf node_modules && npm i && npm run all works)
• close all issues which are solved by dependency updates
• verify develop is up to date with master: git checkout master && git pull && git checkout develop && git merge master
• smoke test to verify all diagrams can be created
• update Release Info
• update CHANGELOG
• merge to master: git checkout master && git merge develop
• create release candidate (npm run release), e.g. v1.0.0-rc.0
  • wait for Release build to create the artifacts
• execute integration test on released artifacts
  • Works on Linux @MaxTru
  • Works on Mac @barmac
  • Works on Windows @philippfromme
• notify QA about the release so they can test it

To be done after integration test was successful or if not issues were fixed.

• create release (npm run release), cf. release schema
  • wait for Release build to create the artifacts

To be done once the release is built.

• write blog post for the Camunda Blog
  • create a draft post on Wordpress
  • send the draft to Christopher Rogers to coordinate the publishing
• (if the Modeler UI appearance changed) update Camunda Modeler screenshots (and potentially text content) in the docs using automation scripts (chore(modeler): update modeler screenshots to 4.9.0 camunda-docs-static#189, chore(modeler): update modeler screenshots to 4.9.0 camunda-docs-manual#1026)
• send all information required to compile the release notice email to the @product-release-presentation-dri role
• reach out to David Paradis so that he updates download version of Camunda Modeler on release day

To be done on release day to announce the release and making it publicly available.

• publish release on Github Releases
• trigger mirroring of release to https://camunda.org/release/camunda-modeler/ via Jenkins
• add new version to updates-server releases JSON file (https://github.com/camunda/camunda-modeler-update-server/pull/66).

To be done once release is publicly anounced.

• publish release via update server (push to live) (https://github.com/camunda/camunda-modeler-update-server/pull/67)
• close current milestone

[MaxTru]

please include @hari-parasuraman for the integration test from Q&A side.
Hari would then include Geetha so that she gets a first peek of how this is performed.