[CF-metadata] Time for 1.0 revision xxx or version 1.1 ?

Ethan Davis edavis at unidata.ucar.edu
Fri Aug 3 09:41:50 MDT 2007


The proposed rules for changes says:

> If the change is accepted, the standard document should be updated, the CF
> convention version number incremented, and the conformance document updated.

But nothing about the actual version number scheme. There has been some 
discussion on the list but I'm wondering if it would be worth spelling 
out some version numbering policy in the change rules. Perhaps a 
paragraph following the above that looks something like:

    Version numbering follows a standard <major>.<minor>[.<maintenance>]
    format. Only the major and minor version numbers are included in the
    "Conventions" global attribute value, "CF-<major>.<minor>". The
    maintenance version number is incremented for changes that will not
    affect software or format. The minor version number is incremented
    for changes that are backward compatible (i.e., an extension to the
    existing convention). The major version number is incremented for
    any changes that would break existing software or cause existing
    datasets to be invalid.


Ethan

Jonathan Gregory wrote:
> Dear John
>
>   
>> How do we fix typos and add information like references etc? 
>>
>>   1. We could start a 1.0 revision xxx for these simple things
>>   2. We could start a 1.1 version for more substantial changes.
>>     
>
> If they are really entirely uncontroversial (like typos or harmless additions
> of information) I think it would be sufficient simply to ask Kyle to amend the
> document by email to this list cc Kyle. If they are more substantial and
> might be the subject of debate, they should be proposed via trac, following the
> new rules.
>
> Best wishes
>
> Jonathan
> _______________________________________________
> CF-metadata mailing list
> CF-metadata at cgd.ucar.edu
> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
>   

-- 
Ethan R. Davis                                Telephone: (303) 497-8155
Software Engineer                             Fax:       (303) 497-8690
UCAR Unidata Program Center                   E-mail:    edavis at ucar.edu
P.O. Box 3000
Boulder, CO  80307-3000                       http://www.unidata.ucar.edu/
---------------------------------------------------------------------------




More information about the CF-metadata mailing list