Release Zeebe Modeler v0.11.0

[MaxTru]

What's inside?

• Improved Input Output Tab (https://github.com/zeebe-io/zeebe-modeler/issues/265)
• Support propagateAllChildVariables on callActivities (https://github.com/zeebe-io/zeebe-modeler/issues/267)
• Support canCopyProperty logic (https://github.com/zeebe-io/zeebe-modeler/issues/248)

Release Checklist

Note: The release manager in charge will be determined by the Camunda Modeler Release Manager (cf. Camunda Modeler Release Checklist)

To be done immediately after creating this issue.

• [x] put up code freeze appointment in calendar (include modeling, qa, infra, zeebe and Team-Support)
• [x] put up release appointment in calendar (include modeling, DevRel and Marketing [Charley Mann & Christopher Rogers])

To be done after code freeze and prior to the release day to prepare and build the release.

• [x] make sure changes in upstream libraries are merged and released
  • bpmn-js, *-properties-panel, *-moddle, ...
  • [x] Release bpmn-js@7.5.0, https://github.com/bpmn-io/bpmn-js/issues/1377
  • [x] Release bpmn-js-properties-panel@0.37.6
• [x] make sure dependencies to upstream libraries are updated and can be installed (rm -rf node_modules && npm i && npm run all works)
• [x] close all issues which are solved by dependency updates
• [x] verify develop is up to date with master: git checkout master && git pull && git checkout develop && git merge master
• [x] smoke test to verify all diagrams can be created
• [x] update CHANGELOG
• [x] merge to master: git checkout master && git merge develop
• [x] create release candidate (npm run release), e.g. v0.11.0-rc.0
  • [x] wait for Travis to build the executables
• [x] execute integration test on released artifacts
  • [x] Works on Linux
  • [x] Works on Mac
  • [x] Works on Windows
• [x] trigger QA for fuzzy testing
• [x] (Since we are DRI for release notice mail): initiate release mail process (see https://github.com/zeebe-io/zeebe-modeler/issues/277#issuecomment-738698587)

To be done after integration test was successful or if not issues were fixed.

• [x] create release (npm run release), cf. release schema
  • [x] wait for Travis to build the executables

To be done on release day to announce the release and making it publically available.

• [x] publish release on Github Releases
• [ ] ~write blog post on Zeebe Blog, if applicable~
• [x] spread the word
  • [x] send release notice email (but exclude Zeebe Modeler)
  • [ ] ~tweet~
• [x] close current milestone

[MaxTru]

Relase Notice Mail Update

• We will not send a release notice mail for Zeebe Modeler, since that would trigger a support notification.

• Since we are - for this stack release (see here) - the DRI for organizing the release presentation, we (ie. @azeghers are also responsible for the relase notice mail). This means we need to do:

• [x] On Friday:

  • [x] Create a copy of the template inside the Google Drive folder Release Notifications
  • [x] Adjust the release versions by applying the information provided in Confluence - Release Dates
  • [x] Share the document with the release managers (All release managers are requested to share information about their release: Blog post links as soon as they are available Release notes aka Change Log (if applicable) The deadline to share the information is the second Monday of a month EOB, i.e., one day before launching the release.)

• [x] On Release Day (Tuesday):

  • [x] Add the recording link to the document
  • [x] Make sure that all links are working properly - if this is not the case, the DRI checks in with the respective release manager
  • [x] Open a new email in Outlook and copy & paste the content from the document into it
  • [x] Ensure that the formatting looks fine in the email
  • [x] Set email subject: Camunda Releases - LIST_OF_RELEASED_PRODUCTS
  • [x] Replace all placeholders like LIST_OF_RELEASED_PRODUCTS, YOUR_NAME, etc.
  • [x] Send the mail to TO: roman.smirnov@camunda.com, richard.weinberg@camunda.com and BCC: alle@camunda.com