Release Camunda Modeler v5.2.0

[philippfromme]

What's inside?

v5.1.0...develop

Linting

General

• properties panel errors toggled when toggling error panel (cf. Toggle Properties Panel Errors When Toggling Error Panel #3014)
• lint error shows element name (this was a regression) (cf. Toggle Properties Panel Errors When Toggling Error Panel #3014)
• error panel styles fixed (cf. Fix Error Panel Styles #3015)

Lint Rules

• connectors (element templates) disallowed prior to Camunda 8 (cf. Disallow Connectors (Element Templates) Prior to Camunda 8 bpmnlint-plugin-camunda-compat#31)
• user task forms must be configured (cf. Add User Task Forms Rule bpmnlint-plugin-camunda-compat#32)

FEEL Editor

• Camunda 8 properties support syntax highlighting for FEEL properties (cf. feat: add Feel editor bpmn-io/properties-panel#158)
• Variables in scope are suggested during typing (cf. feat: pass variables to FEEL editor bpmn-io/properties-panel#171)

Fixes

• The copy of a subprocess is not identical with the original #2438
• form field on the start event creates a business key as well #3050
• DRD image export is broken #3068
• fix(tabs-provider): add missing DMN help menu #3071
• Ellipsis for Errors Not Working #3076
• Adding variable name in literal expression removes DRD view #3048

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 release info (see below)
  • (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
• (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

[philippfromme]

Release candidate can be downloaded here: https://github.com/camunda/camunda-modeler/releases/tag/untagged-67909e3c6f79c1b9c6a8

[philippfromme]

I found an issue with the template lint rule: #3067 I will fix this before the release.

[philippfromme]

I found an issue with the template lint rule: #3067 I will fix this before the release.

Fix is ready and will be integrated before the release (cf. camunda/bpmnlint-plugin-camunda-compat#39).

[philippfromme]

Follow-up Issues

• Feel Editor Not Editable When Clicking on Expanded Editor Area #3072
• Remove Default Value = source of Variable Assignment Value from Newly Created Inputs and Outputs #3073
• Clarify Behavior When Switching between FEEL and Non-FEEL Property #3075

[philippfromme]

Screenshots will be updated shortly by @marstamm. camunda-docs-modeler-screenshots unfortunately doesn't produce usable screenshots on Windows right now (cf. https://github.com/camunda/camunda-docs-modeler-screenshots/issues/39).

[marstamm]

Screenshot PRs:

• chore: update screenshots to modeler v5.2.0 camunda-docs#1134
• chore: update screenshots to modeler v5.2.0 camunda-docs-manual#1276
• chore: update screenshots to modeler v5.2.0 camunda-docs-static#285

[philippfromme]

Documentation PRs will be closed shortly.

[marstamm]

Huh, no new issue? Seems like fake-join is not part of the Camunda Org