Release Camunda Modeler v5.1.0

[MaxTru]

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

[MaxTru]

In Weekly on 31.05. @marstamm volunteered to give @Skaiir a walkthrough of the release steps and to act as backup for the release itself (thanks!)

@Skaiir please pro-actively reach out to @marstamm to get the introduction walkthrough

[MaxTru]

@Skaiir and myself identified that we still miss update of linting rules in accordance with the new form components introced. Val will follow up by creating an issue and working on it.

[CatalinaMoisuc]

@Skaiir and myself identified that we still miss update of linting rules in accordance with the new form components introced. Val will follow up by creating an issue and working on it.

@Skaiir could you please write an update here with the issue you opened?

[Skaiir]

Linting rule issue can be followed here: #3009

[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.

[Skaiir]

@GeethaParthasarathy

General areas of importance:

• Multiselection of elements should work properly in bpmn-js with new visuals in the diagram and in the properties panel.
• Multiselection in dmn-js should also be tested, the behavior should be unchanged from previously, but since we changed it in bpmn-js we have to test for any potential issues.
  • I am aware of one issue when opening both a dmn and bpmn diagram which causes some styles to be overriden in bpmn, please ignore that for now.
• A new context pad for aligning is now present when doing multiselection, this should be tested as well.
  • We are aware of this issue: Alignment can lead to new connections being created bpmn-io/bpmn-js#1693
• Element templates conditional fields in C8 (ignore for now)
• Linting should still work, we made some structural changes to it so please investigate it as well

Fixes:

• Modeler 5 properties panel's keyboard input problem #2990
• fix: reorder close file dialog to match convention #2895
• Saving following file deletion does not replace the deleted file #2925
• fix(deploy): reverse order of input error and description #2924
• Missing/misplaced error messages in Cloud deploy overlay #2918
• fix: make sorting deterministic #2933
• 2873 reopen last tab startup #2893
• fix(overlay): adjust max heights to always fit viewport #2915
• fix(App): use separate linting state #2917
• Improve saving dialog #2300
• fix: improved file dialog consistency across OSes #2971
• Usage of Variables didn't contain a separator #3003
• Error editing properties of Field Injections for Task/Execution Listeners #2989
• Element template name and icon are not displayed in property panel header if template is versioned #2920
• Collapse sub process does not move sequence flow descriptions #2993
• Use explicit "Decision ID" label for the called decision #2725
• Navigating via linting panel references does no clear label editing focus #2961
• No correlationKey in Message Start Event #2983
• form textfield: 'regularExpressionPattern' should be 'pattern' #2919

[Skaiir]

Artefacts can be found here:

https://github.com/camunda/camunda-modeler/releases/tag/untagged-14acd5a2ddc8598eda46

[marstamm]

Should we update the release info to show changes between 5.0.0 and 5.1.0?
Otherwise it would be confusing for user upgrading from 5.

[MaxTru]

Should we update the release info to show changes between 5.0.0 and 5.1.0? Otherwise it would be confusing for user upgrading from 5.

Yes - absolutely. This is part of release procedures

[Skaiir]

Indeed, as well as the changelog, it's all covered in the issue tasks.

[Skaiir]

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

[Skaiir]

Closed without screenshots due to https://github.com/camunda/camunda-docs-modeler-screenshots/issues/37

@philippfromme to take over the next release and create the issue for it :)