You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
(optional) if possible, already create feature branch to update Release Info following our guidelines
What's inside?
M77
issues,v5.23.0...develop
.placeholder
support for element templates (Support placeholders in String and Text templates properties #4330, Support placeholder for properties (String, Text) bpmn-io/bpmn-js-element-templates#92, documentationRelease Checklist
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 withmain
:git checkout main && git pull && git checkout develop && git merge main
npm audit
develop
. Assign to PM, UX and Engineering for reviewCHANGELOG
git checkout main && 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
)The text was updated successfully, but these errors were encountered: