Skip to content

Conversation

@fsimonis
Copy link
Member

@fsimonis fsimonis commented Jan 14, 2026

How to work with this template

  • assign a release manager, who takes care of the process
  • assign each point below to a responsible person, before you continue. Use @member.

Only the release manager should update this post (even tickboxes, due to race conditions in editing). Everybody else should comment on the PR with the progress.

Pre-PR steps

  • Make sure you have the latest main branch locally.
  • Create branch hotfix-vX.Y.Z from main. If needed, git rebase main.
  • Commit fixes to the hotfix branch
  • Check code base w.r.t code formatting (run pre-commit run -va)
  • Update the list of operating systems for the package generation in .github/workflows/release.yml
  • Run tools/releasing/bumpversion.sh MAJOR.MINOR.PATCH to bump the version
  • Look over the updated CHANGELOG.md of the hotfix branch (all)
    • Check for merged lines
    • Add things, if necessary
    • Fix wording and tense
    • Sort the entries lexicographically
    • Extract summary
  • Verify the version changes in:
    • CHANGELOG
    • CMakeLists.txt
    • tools/releasing/packaging/debian/changelog
  • Commit the version bump
  • Push the hotfix branch to the precice repository

Step by step guide

  • Open PR from hotfix-vX.Y.Z to main (use this template)
  • Trigger the system tests using the trigger-system-tests label (release_test suite). After any force-push, remove and add the label again.
  • Fix potential problems on the hotfix branch (all)
  • Reorder the commits for the version bump to be the latest. git rebase -i main
  • Draft release notes
  • Write a draft "blog post" on Discourse
  • Approve the PR with at least two reviews (all)
  • Merge PR to main ( use git merge --no-ff hotfix-vX.Y.Z )
  • Tag hotfix on main vX.Y.Z and verify by running git describe --tags
  • Merge main back to develop and verify by running git describe --tags
  • Triple check that you haven't messed anything up. You can always discard local changes using git reset --hard upstream BRANCH or by cloning the precice repository again and start from scratch.
  • Push main and the vX.Y.Z tag: git push upstream main, git push upstream v3.3.1
  • Push develop: git push upstream develop
  • Wait for the release pipeline
  • Write hotfix text
  • Publish the GitHub hotfix

Post-release

Marketing

See the advertising a workshop section for additional ideas.

Misc

To open a new PR with this template, use this PR template query

@fsimonis fsimonis changed the base branch from develop to main January 14, 2026 09:53
@fsimonis fsimonis marked this pull request as ready for review January 14, 2026 09:54
@fsimonis
Copy link
Member Author

fsimonis commented Jan 14, 2026

MinGW UCRT Debug fails for the same reason we disabled it on develop.

Apart from that, the hotfix is ready for review.

@MakisH
Copy link
Member

MakisH commented Jan 14, 2026

MinGW UCRT Debug fails for the same reason we disabled it on develop.

If this is known to fail and it is anyway something that is not a regression (but something we want to support as well at some point), does it make sense disabling it in this release? Otherwise, the main branch will (still) look broken, which is rather misleading.

@fsimonis
Copy link
Member Author

Otherwise, the main branch will (still) look broken, which is rather misleading.

True. I cherry-picked it to the hotfix.

@fsimonis
Copy link
Member Author

I re-triggered the systemtest and will wait for @IshaanDesai to approve as he requires the hotfix.

Copy link
Member

@IshaanDesai IshaanDesai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I ran a two-scale simulation with the Micro Manager and the hotfix, and can confirm that nested events work as expected.

@fsimonis fsimonis merged commit c8a2733 into main Jan 14, 2026
24 checks passed
@MakisH
Copy link
Member

MakisH commented Jan 14, 2026

Website: versions bumped in:

Not a time to update the Roadmap (bugfix release, and the Roadmap needs more discussion anyway).

@MakisH
Copy link
Member

MakisH commented Jan 14, 2026

Posted on Mastodon and Bluesky. @fsimonis posted on Matrix.

I don't think we need to post anywhere else for this release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants