Hi all - The paragraph in the [rules document](https://urldefense.us/v3/__https://cfconventions.org/rules.html__;!!G2kpM7uM-TzIFchu!ka812U3rXTGiXhFTJ9vi-8Qw_cLVDhuM3XUJIQUi2EWbPJthBpBBagU3XRf6sgpMrh4w-Uane_Q$ ) that mentions deprecation seems focused on recent (or even the most recent) changes/versions. The paragraph starts with > If the change, once implemented in the conventions, subsequently turns out to > be materially flawed … a github issue should urgently be opened to discuss > whether to revoke the change.
This “ocean sigma over z” deprecation would affect all pre-1.9 versions of CF. So there is no change to revoke. How to handle this situation seems unclear, though I lean towards agreement with @JonathanGregory and @pp-mo that it should be more granular than entire versions. Given all that, I think Jonathan’s text looks good. So as not to slow down the resolution of this issue, I propose we move further discussion of the rules around deprecation to a new issue. (I’ll create an issue shortly for further discussion.) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/314*issuecomment-845466770__;Iw!!G2kpM7uM-TzIFchu!ka812U3rXTGiXhFTJ9vi-8Qw_cLVDhuM3XUJIQUi2EWbPJthBpBBagU3XRf6sgpMrh4wI3Wn7rs$ This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
