The removal of Cylc 7 compatibility mode is covered by #6849, however, there are other deprecated Cylc 7 things still lingering, namely:
- Deprecated configurations (e.g.
[cylc][parameters] -> [task parameters]).
- Deprecated event handler template variables (e.g,
%(suite)s).
- Deprecated environment variables (e.g,
$CYLC_SUITE_NAME).
- Deprecated host selection logic (i.e,
[job]batch system and [remote]host).
Further to #7274 we need to agree on a schedule for the removal of these things.
With Cylc 7 compat mode being withdrawn in 8.7, we should delay removal until at least 8.8 to ease the transition for compat-mode workflows.
Furthermore, we should give one full version's worth or warning (i.e, upgrade deprecation warnings to errors and change the message to read "support will be removed at .").
(Also, realistically, we don't have much resource to spare right now!)
So, my suggestion would be 8.9:
- 8.7 - drop compat mode.
- 8.8 - warnings -> errors & add version to deprecation messages.
- 8.9 - removal of support for deprecated syntax.
Will amend REMOVE AT versions and link any relevant BACK COMPAT comments to this issue once decided.
The removal of Cylc 7 compatibility mode is covered by #6849, however, there are other deprecated Cylc 7 things still lingering, namely:
[cylc][parameters]->[task parameters]).%(suite)s).$CYLC_SUITE_NAME).[job]batch systemand[remote]host).Further to #7274 we need to agree on a schedule for the removal of these things.
With Cylc 7 compat mode being withdrawn in 8.7, we should delay removal until at least 8.8 to ease the transition for compat-mode workflows.
Furthermore, we should give one full version's worth or warning (i.e, upgrade deprecation warnings to errors and change the message to read "support will be removed at .").
(Also, realistically, we don't have much resource to spare right now!)
So, my suggestion would be 8.9:
Will amend
REMOVE ATversions and link any relevantBACK COMPATcomments to this issue once decided.