release: 8.0rc3

[hjoliver]

Release Progress

Issue to track the coordinated release of multiple Cylc components.

Required for all minor releases of cylc-flow.

See the release docs for first time instructions and more info.

Prep:

• The release lead should be assigned to this issue.
• Ensure all milestones complete.
• Test cylc-doc (run a test build, perform any required fixes).
• Run cylc-flow functional tests against locally available platforms.
• List the milestones for release below (delete entries as appropriate).

Complete and close milestones for release:

• metomi-isodatetime:
• cylc-flow:
• cylc-ui:
• cylc-uiserver:
• metomi/rose:
• cylc-rose:
• cylc-doc:

PyPi / GitHub releases:

Ensure all Cylc components are pinned to the correct version of cylc-flow.

Trigger releases via GitHub actions.

• metomi-isodatetime
• cylc-flow (bump metomi-isodatetime if required)
• cylc-ui
• cylc-uiserver (update the ui version before releasing)
• metomi-rose (bump metomi-isodatetime if required)
• cylc-rose

Forge (check dependencies match):

Pull requests will be automatically opened on the conda-forge feedstocks
after the pypi releases.

If not, create a new branch, change the version, reset the build number and
update the hash from the PyPi website.
Finally trigger a rerender in a comment.

Ensure dependencies are up to date and follow instructions on the PR. Some
repos may maintain a list of conda dependencies locally.

• metomi-isodatetime (no new release needed)
• cylc-flow
• cylc-ui (not publishing separately?)
• cylc-uiserver
• metomi-rose
• cylc-rose

It make take a couple of hours for a release to become available.
Use conda search <package> to determine when it's ready.

Misc (after the above has been completed):

• cylc-doc
  • bump intersphinx versions if required (cylc-doc/src/conf.py)
  • review deployment instructions
  • deploy (run the "deploy" workflow on GitHub Actions) (can be re-deployed later if necessary)
• metomi-rose
  • build & deploy documentation - Gh pages.add 2.0rc3 metomi/rose#2595
• discourse post

Metadata:

Update project versions to the next milestone
AND pin downstream components to the next cylc-flow dev release.

• cylc-flow - Bump to next dev version cylc-flow#4893
• cylc-uiserver (pin to latest cylc-flow) - Bump version. cylc-uiserver#358
• cylc-rose (pin to latest cylc-flow) - Bump versions cylc-rose#143
• metomi-rose - Bump version metomi/rose#2596

Finally:

• close this issue 🚀

[oliver-sanders]

When releasing cylc-flow, remember to git grep nightly and switch any cylc-doc URLs over to latest.

[oliver-sanders]

The UI has received a string of dependency changes lately so it's worth giving a little more attention to testing the UI before pushing the release button this time around.

[hjoliver]

When releasing cylc-flow, remember to git grep nightly and switch any cylc-doc URLs over to latest.

There are no matches in cylc-flow. Should there be?

[oliver-sanders]

Ah sorry, it was an RC4 PR which has not yet been merged - cylc/cylc-flow#4860

[oliver-sanders]

@hjoliver

Sorry my bad, there's a missing instruction here:

Trigger releases via GitHub actions.

The repos are listed in release order, however, the issue template doesn't tell you to do them in order.

No probs, don't need to go closing the PRs but they will fail until the relevant bits have been released due to version pinning.

cylc-uiserver (update the ui version before releasing)

There is a GH action which updates the UI from the official build automatically, follow the link in the above line. Note the UI must be released before it can be updated in the UIS.

[oliver-sanders]

Complete and close milestones for release:

No need to close the milestones, the release actions do this for you automatically.

[oliver-sanders]

Updated the instructions - #154

[oliver-sanders]

Ticked off the "discourse post" item, good to close?