Release Camunda Modeler v5.1.0

What’s inside?

v5.0.0...develop

Key-Changes:

• Mixpanel telemetry data
• form-js regexpattern bug
• bpmn-js UX improvements
• removed new label
• …

Release Checklist

To be done immediately after creating this issue.

• put up code freeze appointment in calendar (include modeling, qa, infra, and Team-Support)
• 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 before the code freeze.

• inform QA about the release and its details so they can prepare for testing
• Get in touch with the team (PM, UX and Engineering side), to clarify what topics will be included in the Release and their priority. Use this information to start preparing a concept for the blog post (see below) and release info (see below)
  • @christian-konrad to write blogpost for this one
  • (optional) if possible, already create feature branch to update Release Info following our guidelines

To be done after code freeze to prepare and test 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
• smoke test to verify all diagrams can be created
• update Release Info
  • create a draft following our guidelines and based on priorities which were aligned with the team (PM, UX, and Engineering side)
  • create PR to merge the draft into develop. Assign to PM, UX and Engineering for review
• update CHANGELOG
• verify develop is up to date with master: git checkout master && git pull && git checkout develop && git merge master
• merge to master: git checkout master && git merge develop
• create release candidate (npm run release), cf. release schema; e.g v1.0.0-rc.0
  • wait for release build to create the artifacts
• execute integration test on released artifacts
  • Works on Linux
  • Works on Mac
  • Works on Windows
• notify QA about the release so they can test it

To be done to build the release after release testing completed.

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

To be done once the release is built.

• publish release on Github Releases
• trigger mirroring of release to Camunda Download Center via Jenkins
• write blog post for the Camunda Blog
  • duplicate our blog post template via PA duplicate
  • add your contents to the newly created post
  • set yourself as the post author
  • share the post with your colleagues for review
  • send the draft to Christopher Rogers to double check it and coordinate publishing
• (if the Modeler UI appearance changed) update Camunda Modeler screenshots (and potentially text content) in the docs using automation scripts
• send all information required to compile the release notice email to the @product-release-presentation-dri role
• request marketing to update the downloads page via request form
• add new version to update server releases

To be done once release is publicly announced on release day.

• publish release via update server (push to live)
• close current milestone

[Skaiir]

I just got the rc out early so that we could start testing, otherwise timing would be a bit short.

[Skaiir]

I’ve had a discussion with @GeethaParthasarathy. She will handle QA for the 5.1 release.

Testing will occur on Friday (8th July), this leave us time in case the testing period extends further. Thursday afternoon, Geetha and I will conduct a sync to discuss the major areas of change and hence testing focus.