[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
[x] update Camunda Modeler screenshots (and potentially text content) in the docs by running screenshots workflow. Download artifacts and create PRs for:
What's inside?
v5.15.1...develop
Noteworthy items:
Release Checklist
To be done immediately after creating this issue.
@desktop-modeler-release-manager
)To be done before the code freeze.
To be done after code freeze to prepare and test the release.
bpmn-js
,dmn-js
,*-properties-panel
,*-moddle
,camunda-bpmn-js
,form-js
, ...rm -rf node_modules && npm i && npm run all
works)develop
is up to date withmaster
:git checkout master && git pull && git checkout develop && git merge master
develop
. Assign to PM, UX and Engineering for reviewCHANGELOG
git checkout master && git merge develop
npm run release:rc -- [preminor|premajor|prerelease]
), cf. release schemaTo be done to build the release after release testing completed.
npm run release
), cf. release schemaTo be done once the release is built.
To be done once release is publicly announced on release day.
live
)