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

bump deprecation warnings from Cylc 9 to 8.x #4853

Merged
merged 2 commits into from
May 5, 2022

Conversation

oliver-sanders
Copy link
Member

[meeting 2022-05-04]

  • Logically Cylc 9 should come at the next configuration breaking change, however, that isn't planned for some time.
    (note the Python API should not break flow.cylc compatibility)
  • So we will remove back-support in the 8.x series rather than waiting for Cylc 9.

Requirements check-list

  • I have read CONTRIBUTING.md and added my name as a Code Contributor.
  • Contains logically grouped changes (else tidy your branch by rebase).
  • Does not contain off-topic changes (use other PRs for other changes).
  • Applied any dependency changes to both setup.cfg and conda-environment.yml.
  • Does not need tests (why?).
  • No change log entry required (why? e.g. invisible to users).
  • No documentation update required.

* Logically Cylc 9 should come at the next configuration breaking
  change, however, that isn't planned for some time.
  (note the Python API should not break flow.cylc compatibility)
* So we will remove back-support in the 8.x series rather than waiting for
  Cylc 9.
@oliver-sanders oliver-sanders added this to the cylc-8.0rc4 milestone May 4, 2022
@oliver-sanders oliver-sanders self-assigned this May 4, 2022
@hjoliver
Copy link
Member

hjoliver commented May 4, 2022

Logically Cylc 9 should come at the next configuration breaking change,

Historically, I bumped the major version along with "major" (and often internal) changes. However, the new way is better!

@oliver-sanders
Copy link
Member Author

Historically, I bumped the major version along with "major" (and often internal) changes. However, the new way is better!

6, 7 & 8 all had network layer changes which I think were also a valid reason to bump the major version.

Co-authored-by: Hilary James Oliver <hilary.j.oliver@gmail.com>
@datamel datamel self-requested a review May 5, 2022 09:23
Copy link
Contributor

@datamel datamel left a comment

Choose a reason for hiding this comment

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

Approving. No problems found for me. Thanks @oliver-sanders. Will merge after CI check.

@datamel datamel merged commit fd4e4f1 into cylc:master May 5, 2022
@oliver-sanders oliver-sanders deleted the cylc-9->8.x branch May 5, 2022 09:38
wxtim added a commit to wxtim/cylc that referenced this pull request May 6, 2022
…ins-localhost

* expand_platforms_section:
  glblcfg: split comma separated platform definitions
  tests/u: parsec/test_util unittest->pytest
  bump deprecation warnings from Cylc 9 to 8.x (cylc#4853)
  Update tests/functional/execution-time-limit/04-polling-intervals.t
  Stop a few deprecation warnings in Cylc7 back compat mode
  Add tests
  Add polling interval test and change log entry.
  Set excecution polling delays correctly
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants