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

8.0.0 #157

Closed
26 tasks done
wxtim opened this issue Jul 25, 2022 · 1 comment
Closed
26 tasks done

8.0.0 #157

wxtim opened this issue Jul 25, 2022 · 1 comment
Assignees
Labels
release An issue for keeping track of a Cylc release

Comments

@wxtim
Copy link
Member

wxtim commented Jul 25, 2022

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).

Milestones for release:

The release actions close the milestones for you automatically.

  • 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.

(logical release order)
R1 = """
   cylc_flow & metomi_rose => cylc_rose
   cylc_flow & cylc_ui => cylc_uis
"""
Info on version pinning
Cylc plugins (i.e. cylc-rose and cylc-uiserver) are "pinned" to the minor version of cylc-flow. E.G. if the cylc-flow version is 8.1.2 the plugins should be pinned to 8.1.

More Information
  • cylc-flow
  • cylc-ui
  • cylc-uiserver (update the ui via GH action first)
  • metomi-rose
  • cylc-rose
  • cylc-sphinx-extensions

Forge (check dependencies match):

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

If the PR doesn't get opened automatically
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.

  • cylc-flow
  • cylc-ui (decide if "dead-ending" or what) later
  • 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 (manual process ATM)
  • discourse post

Metadata:

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

  • cylc-flow
  • cylc-uiserver (pin to latest cylc-flow)
  • cylc-rose (pin to latest cylc-flow)
  • metomi-rose

Finally:

  • close this issue 🚀
@wxtim wxtim added the release An issue for keeping track of a Cylc release label Jul 25, 2022
@oliver-sanders
Copy link
Member

oliver-sanders commented Jul 26, 2022

  • nice to have fix for the docs in cylc-sphinx-extensions. (requires release of cylc-sphinx-extensions before cylc-doc build/deploy).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release An issue for keeping track of a Cylc release
Projects
None yet
Development

No branches or pull requests

3 participants