Release camunda-modeler v5.15.0

github-actions[bot] commented 1 year ago

What's inside?

FEAT: move Call Activity to Sub Processes group in options menu (bpmn-js-create-append-anything#14)
FEAT: add Input propagation group (#3793)
FEAT: visually show deprecated templates in properties panel (bpmn-js-element-templates#11)
FEAT: suggest variables from form schema (#3780)
FEAT: do not hide overlays on canvas move per default (bpmn-io/diagram-js#798)
FIX: allow to create connection + event-based gateway (bpmn-io/bpmn-js#1490)
FIX: correct copy of default sequence flow elements (bpmn-io/bpmn-js#1935)
FIX: make breadcrumb styling more robust (bpmn-io/bpmn-js#1945)
FIX: remove Outputs group from error end events (#3782)
FIX: show all FEEL errors in Problems panel (#3806)
CHORE: example data is no longer scoped to the element that defines it (#3728)

To be done immediately after creating this issue.

To be done before the code freeze.

[x] inform QA about the release and its details so they can prepare for testing
[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] make sure dependencies to upstream libraries are updated and can be installed (rm -rf node_modules && npm i && npm run all works)
[x] verify develop is up to date with master: git checkout master && git pull && git checkout develop && git merge master
[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] compile a list of blog worthy changes as input to release blog
[x] merge to master: git checkout master && git merge develop
[x] create release candidate (npm run release:rc -- [preminor|premajor|prerelease]), cf. release schema
- [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] update Camunda Modeler screenshots (and potentially text content) in the docs by running screenshots workflow. Download artifacts and create PRs for:
- [x] camunda-docs-static
- [x] camunda-docs-manual
- [x] camunda-docs-platform
[x] provide content to the release presentation and notice
[x] trigger downloads page update via marketing 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] announce the release via the Camunda internal #c8-release-announcements channel
[x] close current milestone

philippfromme commented 1 year ago

github-actions[bot] commented 1 year ago

Assigned @nikku as the next release commander.