Hi @erget, publishing `1.[78].1` (1.6 already has its date) in Spetember alongside 1.9 is fine by me.
If I understand the procedure correctly, we'd take a branch from the tagged commit, add the date and revision history to the branch and then tag that branch's commit as 1.x.1. Sounds good. We'd then update https://urldefense.us/v3/__https://cfconventions.org/documents.html__;!!G2kpM7uM-TzIFchu!lbgyUZxB2DcsnaKKFuaaVpGB8ubBWcCtKrTOZx-hdejV1lJfjWKUNyr1lslP-7qajGxu6RST32g$ to add the new versions. -- 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/329*issuecomment-865715435__;Iw!!G2kpM7uM-TzIFchu!lbgyUZxB2DcsnaKKFuaaVpGB8ubBWcCtKrTOZx-hdejV1lJfjWKUNyr1lslP-7qajGxu_2-ODeU$ 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.
