Release Camunda Modeler v4.12.0

[MaxTru]

Camunda Modeler 4.12.0 Release

This is to track the planned Camunda Modeler v4.12.0 release planned for 11.01.2022.

This release will only include the absolute key changes we need for Cloud 1.3.

:warning: READ THIS :warning:

• We will not merge develop to master (as we usually do) but only selectively include needed commits. The develop to master merge will happen as part of a seperate Release Camunda Modeler v5.0.0-alpha0 release.
• Because of this, we want to make quick progress. Hence we will build the 4.12.0 release artifact ASAP (as soon as all relevant issues are ready)

What's inside?

M51

• Form linting updated to cover Zeebe 1.3
• Support for zeebe:assignmentDefinition on bpmn:userTasks
• Keep original IDs when copy / pasting

Release Checklist

To be done immediately after creating this issue.

• [x] put up code freeze appointment in calendar (include modeling, qa, infra, and Team-Support)
• [x] put up release appointment in calendar (include modeling, DevRel and Marketing [ Christopher Rogers ])
• [x] add Slack role to release manager (@modeling-release-manager)

To be done before the code freeze.

• [x] inform QA about the release and its details so they can prepare for testing
  • [x] Inform @GeethaParthasarathy about our approach
• [x] 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)
  • [x] (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.

• [x] make sure changes in upstream libraries are merged and released
  • bpmn-js, dmn-js, *-properties-panel, *-moddle, camunda-bpmn-js, form-js, ...
• [x] Selectively bring commits for the above features into master
• [x] make sure dependencies to upstream libraries are updated and can be installed (rm -rf node_modules && npm i && npm run all works)
• [x] close all issues which are solved by dependency updates
• [x] smoke test to verify all diagrams can be created
• [x] update Release Info
  • [x] create a draft following our guidelines and based on priorities which were aligned with the team (PM, UX, and Engineering side)
  • [x] create PR to merge the draft into develop. Assign to PM, UX and Engineering for review
• [x] update CHANGELOG
• [x] ~verify develop is up to date with master: git checkout master && git pull && git checkout develop && git merge master~
• [x] ~merge to master: git checkout master && git merge develop~
• [x] create release candidate (npm run release), cf. release schema; e.g v1.0.0-rc.0
  • [x] wait for release build to create the artifacts
• [x] execute integration test on released artifacts
  • [x] Works on Linux
  • [x] Works on Mac
  • [x] Works on Windows
• [x] notify QA about the release so they can test it

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

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

To be done once the release is built.

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

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

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

[MaxTru]

Decided together with Bea and Max:

• We will not have a blog post for this release (not enough features)
  • @smbea will talk to Cloud team (@menski) and ask them to include a basic sentence in their release blog post, that Camunda Modeler 4.12 supports assignmentDefiniion

cc @andreasgeier @nikku

[smbea]

The release candidate has been tested (in all OS and also by QA).

A bug regarding keeping original ids with copy-paste was found (https://github.com/camunda/camunda-modeler/issues/2621). We will hold off until end of next week to build the release (with this bug fix, if implemented).

[smbea]

The Github release was published: https://github.com/camunda/camunda-modeler/releases/tag/v4.12.0. The checklist will be continued in January, closer to the official release date.