Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions source/Reviewers/curaterelease.rst
Original file line number Diff line number Diff line change
Expand Up @@ -138,6 +138,9 @@ and the other will review it (**developer** and **reviewer** below).

* Disable the ``Require Linear History`` setting
* Set the only allowed merge method as ``merge`` (remove ``squash``)
* Disable the ``Require branches to be up to date before merging`` setting
(if commits have been pushed to ``main`` since the release, this would
require ``stable`` to be updated with those, which isn't desired).

* The **developer** will make the hotfix change, making sure the branch has been
created from ``stable``. Open a PR for this change targetting ``stable`` and
Expand Down
1 change: 1 addition & 0 deletions source/Reviewers/releases/milestones.rst
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,7 @@
Milestones and Projects
=======================


#. Tidy up all pull requests and issues for the completed milestone in the
Simulation Systems Review and Issues Trackers.

Expand Down
2 changes: 2 additions & 0 deletions source/Reviewers/releases/other_repos.rst
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,8 @@ Other Repositories
* moci
* um_aux
* socrates-spectral
* gcom
* rose_picker
* mule (if not already done as part of a release)
* shumlib (if not already done as part of a release)

Expand Down
4 changes: 3 additions & 1 deletion source/Reviewers/releases/umdp_release.rst
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,8 @@ UMDP Release
URL.

* It is also worth checking no URLs are out of date.
* With a reviewer, follow the :ref:`release process <github-releases>`.
* Open a PR for this branch, targetting ``main`` and get this reviewed and
committed.
* Once on, follow the :ref:`release process <github-releases>` with a reviewer.
* Ensure the action to publish the documentation has successfully completed and
the `new documentation is available <https://metoffice.github.io/um_doc/>`_.