Dear all Thanks for pointing it out, Leon @adigitoleo. I think @zklaus is right that we could add a "replacement" i.e. a sort of macro in AsciiDoc for the current version number, so that only one occurrence needed to be changed. I am not familiar with the build process so I won't volunteer to do that. Is there a checklist for making a new version, to which this could be added? I think @davidhassell must know. As Daniel @erget says, it would be easy to fix the typo, and I'm sure we would approve the change as a defect issue for it . But could we agree to modify the live 1.9 document _immediately_? There would be no point in agreeing a defect correction to 1.9 which wasn't going live until 1.10 in this case!
Best wishes and happy 2022 to the CF community Jonathan -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/343*issuecomment-1004637875__;Iw!!G2kpM7uM-TzIFchu!lcGrz1UD4c19TlIyQJvGIhD4Ap6e2doFs2H-l36Yi7Q90AaOtFLhEqnMyqW-ecl42OedBQ6f-QU$ You are receiving this because you are subscribed to this thread. Message ID: <cf-convention/cf-conventions/issues/343/[email protected]> This list forwards relevant notifications from Github. It is distinct from [email protected], 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 [email protected].
