Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release camunda-modeler v5.28.0 #4521

Closed
36 of 41 tasks
github-actions bot opened this issue Sep 12, 2024 · 8 comments
Closed
36 of 41 tasks

Release camunda-modeler v5.28.0 #4521

github-actions bot opened this issue Sep 12, 2024 · 8 comments
Assignees
Labels
Milestone

Comments

@github-actions
Copy link

github-actions bot commented Sep 12, 2024

What's inside?

Changelog, v5.27.0...develop, milestoned tasks.

Release Checklist

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)

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 potential new engine versions are available and marked correctly (alpha/stable)
  • make sure dependencies to upstream libraries are updated and can be installed (rm -rf node_modules && npm i && npm run all works)
  • verify develop is up to date with main: git checkout main && git pull && git checkout develop && git merge main
  • close all issues which are solved by dependency updates
  • ensure that the modeler is free of major security vulnerabilities via npm audit
  • smoke test to verify all diagrams can be created
  • update Release Info
  • update CHANGELOG
  • compile a list of blog worthy changes as input to release blog
  • merge to main: git checkout main && git merge develop
  • create release candidate (npm run release:rc -- [preminor|premajor|prerelease]), cf. release schema
  • 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.

To be done once the release is built.

To be done as a post-release activity.

To be done once release is publicly announced on release day.

@github-actions github-actions bot added ready Ready to be worked on release labels Sep 12, 2024
@nikku nikku added this to the M81 milestone Sep 16, 2024
@nikku nikku added the in progress Currently worked on label Sep 20, 2024 — with bpmn-io-tasks
@nikku nikku removed the ready Ready to be worked on label Sep 20, 2024
@barmac
Copy link
Collaborator

barmac commented Sep 23, 2024

IMO "lint first item access" is a general feature as it's shared among all editors. So it does not belong to BPMN only.

@barmac
Copy link
Collaborator

barmac commented Sep 23, 2024

@nikku #4542

@nikku
Copy link
Member

nikku commented Sep 23, 2024

Release candidate available for testing here.

@nikku
Copy link
Member

nikku commented Sep 23, 2024

Minor bump: We had to re-build the RC, due to a blocking issue discovered in pre-release testing / modeler integration.

@nikku nikku added the fixed upstream Requires integration of upstream change label Sep 30, 2024 — with bpmn-io-tasks
@nikku nikku removed the in progress Currently worked on label Sep 30, 2024
@nikku
Copy link
Member

nikku commented Oct 9, 2024

All release activities executed. Closing this issue. ✔️

@nikku nikku closed this as completed Oct 9, 2024
@bpmn-io-tasks bpmn-io-tasks bot removed the fixed upstream Requires integration of upstream change label Oct 9, 2024
Copy link
Author

github-actions bot commented Oct 9, 2024

Created follow up release issue.

Assigned @marstamm as the next release commander.

@nikku
Copy link
Member

nikku commented Oct 9, 2024

image

🤩

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants