I've prepared a PR at #316. It mostly contains @JonathanGregory's wording with two small changes identified by separate commits. Feel free to comment on the proposed wording.
I wasn't entirely sure about how to handle the remaining things of the release checklist, namely: * Authors updated in cf-conventions.adoc? * Next version in cf-conventions.adoc up to date? Versioning inspired by SemVer. * Conformance document up-to-date? Can you provide me some assistance on how this should be done? --- @taylor13 I agree with your suggestions and hope that the current PR is sufficient in **not** naming those things. @chris-little I also fully agree that leap seconds should not be ignored, and indeed I have use cases where I really want to represent times within those leap seconds. However an even bigger problem is that I want to unambiguously specify at least **most** of the date-times. Currently there's obviously **some** way people handle the conversion of time values into date-times, but it is not written down, so datasets which might cross leap seconds are ambiguous. I'll try to put effort in advancing a method of properly handling those missing leap seconds in the future, but I honestly think that that should be the second step and I like doing things step by step. Regarding this issue, I only see two options to treat the importance of leap seconds: * [ ] add another note to the conventions that leap seconds are really important, but still can't be represented at the moment * [ ] don't do that and instead think more about forwarding #148 or the like I strongly favor the second option. --- And thank you all again for being so positive about this thing 🎉 -- 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/313*issuecomment-795797877__;Iw!!G2kpM7uM-TzIFchu!lssbDyUo1K47-8LQxldoAKfNt61QCLdE9z3ruKLlI5aJA3r6NOgUyarZa-TVPWQmIiZbIV7-m10$ 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].
