It took me awhile to understand the meaning of the term `attribute-version`. Perhaps `current-version-as-attribute`?
I like the definitive nature of updating the version from `1.10-draft` to `1.10` for release and then immediately updating to `1.11-draft`. It leaves an artifact (source zip file) that is clearly marked as a full release. On the other hand, this is a documentation project not a software project and we distribute document artifacts not source artifacts. However, it might be more of an issue depending on where the CF DOI conversation about version specific DOIs goes. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/343*issuecomment-1007587182__;Iw!!G2kpM7uM-TzIFchu!itXafRG3RTx6TTruC04c6mYK8PUHq8wrIPEwQR7qCkUMJZS8G8Txe825ye7H3aq9q7X2kyP_juE$ 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].
