Thanks @zklaus, the PR looks pretty cool. Also yes, happy new year everybody! :)
I've requested also the input of @davidhassell since he's more heavily involved in the release process. @JonathanGregory, I propose that we proceed as follows: - If we can agree on an approach for a longer-term fix, e.g. by accepting the changes proposed in #344, then we cherry-pick those on top of 1.9 and make a patch release to correct the defect. - If the long-term approach takes longer to clarify, i.e. more than a week or so, we manually correct the defect in 1.9. What do you think? Cheers, Daniel -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/343*issuecomment-1005688209__;Iw!!G2kpM7uM-TzIFchu!gAL93PODqwDjFufg1W1CiFpJ10SK0I9_idYJFg-4LheaCKoGQtk4NwsRqBF8kKH60a_Yth8uzn8$ 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].
