https://wiki.opm-project.org/index.php?action=history&feed=atom&title=Notes_for_managing_release_%28since_2026.04%29 2026-04-15T01:59:45Z Revision history for this page on the wiki MediaWiki 1.35.13 https://wiki.opm-project.org/index.php?title=Notes_for_managing_release_(since_2026.04)&diff=1913&oldid=prev 2026-04-14T15:01:48Z

<p>Detailed manual for the release managers (incomplete).</p> <p><b>New page</b></p><div>The responsibility of the release manager is to<br /> * Create release branch and tag release candidates for testing<br /> * Build binary packages for testing<br /> * Backport bugfixes and other high-priority pull requests<br /> * Update the version of the modules<br /> <br /> Note that all steps have to be repeated for modules &#039;&#039;opm-common&#039;&#039;, &#039;&#039;opm-grid&#039;&#039;, &#039;&#039;opm-simulators&#039;&#039;, and &#039;&#039;opm-upscaling&#039;&#039;<br /> <br /> ==Creation of the first release candidate==<br /> # Create a new branch for the first release candidate.<br /> ## The branch naming convention is &#039;&#039;year.month&#039;&#039;, e.g. 2026.04, and we currently have releases in months 04 and 10.<br /> ## Open the &#039;&#039;dune.module&#039;&#039; change the Version and Label to the release candidate 1, e.g. change 2026.04-pre to 2026.04-rc1.<br /> ## Add and commit the changes to the &#039;&#039;dune.module&#039;&#039;.<br /> ## Give the branch the tag of the release candidate: &#039;&#039;branch_name&#039;&#039;/rc1. Make sure the tag is placed after the version change was committed. If it was placed before, delete the tag and create it again after the commit.<br /> ##: git tag 2026.04/rc1<br /> # Push the branch into the OPM github remote.<br /> #: Push the tag as well.<br /> # Update the version of the master branch.<br /> #: This is done via a normal pull request from your forked repository. Update the Version and Label in &#039;&#039;dune.module&#039;&#039;, e.g. from 2026.04-pre to 2026.10-pre. Note that master is always ahead of release.<br /> # Update the release version in the shell scripts in &#039;&#039;opm-utilities&#039;&#039;.<br /> #: Relevant files are &#039;&#039;release-scripts/opm-backport-pr.sh&#039;&#039; and &#039;&#039; release-scripts/opm-release-install-test.sh&#039;&#039;.<br /> #: This is done via a normal pull request like the version-updating of the master branch.</div>

Michaltoth