Re: [CF-metadata] [cf-convention/cf-conventions] Single source version (PR #344)
I have added a fancified version of the version handling. Let me know what you think or if you want me to explain a bit more. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/344*issuecomment-1007108115__;Iw!!G2kpM7uM-TzIFchu!hTgR6yWW07-VIEpVyzfJT3j9NlNJuxLZhy-Qs_yjJ14AqXYgLtz9YZ_lvvyLKFHNfQADgy5yQjk$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] Single source version (PR #344)
@zklaus pushed 1 commit. ff0a539a242555b27cd6aa5018e6e9a0c65b1530 Fancify single sourced version -- View it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/344/files/1bae8aead25c12a9b0f7cd0af7cfd636a8ed1ca3..ff0a539a242555b27cd6aa5018e6e9a0c65b1530__;!!G2kpM7uM-TzIFchu!l3zFgo2SFQp858jyayGeZ7ZYiZD29X1MHHR7seV2wuw-VrtDUxLkdQusrVng8mJtSxtQ4PnKAsk$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] Cutting version 1.10 (Issue #345)
Hello all, My (current) thoughts on the new release question: I'm not sure about cutting 1.10 to fix just this defect. Given that it can be fixed in the latest CF-1.10 draft, is that not sufficient to tide us over to the whenever CF-1.10 is released? A few years ago we agreed that one release, or perhaps two releases, per year was a good balance; which to me, at least, means that any extra release in the year should be reserved for either getting new functionality out to users with production time constraints, or else correcting a serious error. I'm not sure that this defect (important as it is!) adds new features, nor warrants the "serious" label. I like the idea of per-release history entries, and "(No) change agreed" issue labels. I would find those very useful. [Daniel wrote](https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/345*issuecomment-1006644633__;Iw!!G2kpM7uM-TzIFchu!hOibaETdBKBrgpir550s20Qgv0K4JPNqTVGMPwPWHbh_TsLOJvVB3rqUEqcGtYbWStY00KX05FY$ ): > Barring that, this can be discovered by pulling up closed PRs and sorting by > date, then checking what was merged into main between releases - that is > however more laborious, so labeling the PRs pre-merge would be the most > expedient in my view. That is exactly what I did when applying many of those milestones - and it was indeed laborious. Labelling them at merge-time would be a great addition to the workflow. Setting a milestone on a PR (or issue) is very similar to setting a label - it's on the right hand panel just below where the label-setting feature is. I have just created a 1.10 milestone (via https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/milestones__;!!G2kpM7uM-TzIFchu!hOibaETdBKBrgpir550s20Qgv0K4JPNqTVGMPwPWHbh_TsLOJvVB3rqUEqcGtYbWStY0SJa4pZs$ ). Thanks, David -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/345*issuecomment-1006955695__;Iw!!G2kpM7uM-TzIFchu!hOibaETdBKBrgpir550s20Qgv0K4JPNqTVGMPwPWHbh_TsLOJvVB3rqUEqcGtYbWStY0sY8vyaw$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] Single source version (PR #344)
@zklaus pushed 1 commit. 1bae8aead25c12a9b0f7cd0af7cfd636a8ed1ca3 Add -draft suffix to version -- View it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/344/files/cf497a5759c3db2b36ff924381eb1aaab0067426..1bae8aead25c12a9b0f7cd0af7cfd636a8ed1ca3__;!!G2kpM7uM-TzIFchu!iDa0AGkFyxXRJo9tT-1BSCm8MUvZDnD1P0rvyy3O12UvlWY_u5ItiT_C7adbGmIE1pK5QvItZ8I$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] Cutting version 1.10 (Issue #345)
I agree, per-release headers in History would be helpful. @JonathanGregory - I like the idea of closing inactive issues after some period of dormancy and adding a "No change agreed" label to those issues. I also like the idea of adding a "Change agreed" label to issues as they are agreed (and PRs merged). -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/345*issuecomment-1006764920__;Iw!!G2kpM7uM-TzIFchu!gSsjmfg_GZkiRu3o-z6W_nLiNQBwBB0ZRkc4yr7gJht66UCG7_6D8UdI64jxqFtOweVJ20HAGVE$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] Cutting version 1.10 (Issue #345)
> @JonathanGregory I agree that a per-release entry in History would make sense. OK. If others agree, this is something we could introduce in 1.10, and it might not be too hard to insert those headings for all the previous versions. > What you propose regarding labels would work, although it might be simpler if > we track them by pull requests. ... This has been made easy for 1.9 as shown > by [this > filter](https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pulls?q=is*3Apr*is*3Aclosed*sort*3Aupdated-desc*milestone*3A1.9__;JSslKyUrJQ!!G2kpM7uM-TzIFchu!h1cVF0ZY_-rnSXxaKt6O3ektrxVFu9le3PS-9SdJ89aMd1smc48A9OhKLSNWiwFbMoc5PeLCVQk$ > ) showing those PRs that were manually tagged as going into 1.9. ... > Labeling the PRs pre-merge would be the most expedient in my view. Thanks. That is neat. How do you tag the PRs in this way? I agree that it would be sensible to do that as it is agreed that a PR will be merged at the next release. However, this doesn't tag the issues, does it? Therefore I think it would still be useful to add a label to the issue once it's agreed to update the convention, for instance "Change agreed". This label would remain forever, and by following the link in the issue to its PR, tagged in the way you describe, you could find out which version it affected. I would also propose a complementary label "No change agreed", to be applied to any issue which we close because it doesn't seem that it's going to reach a conclusion. Of course any closed issue could be reopened and the label removed. I feel that it's better to close issues than to leave them forever dormant. Do others agree, or am I being tempted by excessive tidiness? -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/345*issuecomment-1006751005__;Iw!!G2kpM7uM-TzIFchu!h1cVF0ZY_-rnSXxaKt6O3ektrxVFu9le3PS-9SdJ89aMd1smc48A9OhKLSNWiwFbMoc5UPAXQNc$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] Cutting version 1.10 (Issue #345)
For reference, in ESMValTool we use just the process that @erget described to generate the changelog using [this script](https://urldefense.us/v3/__https://github.com/ESMValGroup/ESMValTool/blob/main/esmvaltool/utils/draft_release_notes.py__;!!G2kpM7uM-TzIFchu!mEdDWp3uFu7z4p9FhhD25ii80KIQFhpsRbJBmtnpWrqdONx9ZPuMEizM_bMYvJyqFiYtzGi4Pa4$ ). We are considering replacing this with one of the many available standard solutions that do a similar thing. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/345*issuecomment-1006748698__;Iw!!G2kpM7uM-TzIFchu!mEdDWp3uFu7z4p9FhhD25ii80KIQFhpsRbJBmtnpWrqdONx9ZPuMEizM_bMYvJyqFiYtpVW4UVk$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] DOIs for CF Convention releases? (#127)
@castelao : thanks, I agree with your approach. Following the theme of keeping things simple unless there is a clear need, I suggest using your listed fields plus `Description` for now, and more can be added later if needed. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/127*issuecomment-1006709886__;Iw!!G2kpM7uM-TzIFchu!lA-HsrxitpRQOlbep429lHCT15H6cIDgDlXUzzbNIO5bXN30Et2Wnemthvml9lhxhYqbgWb5TRE$ You are receiving this because you commented. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] Single-source the version number (Issue #343)
I prefer the more terse formulation. Replacing the space with a dash, so `1.10-draft`, would be similar to a well known pattern for software versioning of appending `-SNAPSHOT` or `-mmddhhss` to a version number. Perhaps a bit more obvious than `1.10 draft` but still terse. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/343*issuecomment-1006698450__;Iw!!G2kpM7uM-TzIFchu!godn4COKgWP6Uv5u0oy0fJnLstAZU8MVnx0XCA2sh6VX-5VLiwvzSLH5NvE9zgc8JE6W3ZnuhB8$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] DOIs for CF Convention releases? (#127)
@martinjuckes , thanks for raising this point. I think it is a good idea to have a description associated with the DOI. To clarify, Zenodo is quite convenient and I've been a happy user but the price is that we must conform with their resources. A direct DOI registration provides more fields and more flexibility for us. The DOI handle that we see is like a primary key in a database. When we use a DOI we are usually interested in the fields associated with that primary key. Although one of the DOI fields is the URL for the landing page, the goal is not to replace our use of URLs with DOIs. There are several possible fields, but the required ones are: - Location (URL) - Creators - Title - Publisher - Publication Year - Resource Type As suggested by @martinjuckes I strongly recommend adding 'Description' of type 'abstract'. I also suggest starting with these fields and once we get an agreement on those we might consider the rest of the possible list. Since DOI is meant for machine-to-machine communication, the landing page URL is usually a page with human-readable information. I usually use a dedicated landing page, brief but with more space than the abstract field, pointing what are the resources and where to find them. My suggestion is to use the cf-conventions.org as the associated URL for now, and once we concluded the requirements we can consider improvements. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/127*issuecomment-1006690235__;Iw!!G2kpM7uM-TzIFchu!ibY5wKZST_-l8VD9mzfbo8cjV40dWYrPCpsjVgiqbgouwi6tk8loKEg1WbCWvo8IaxzHdNIXad4$ You are receiving this because you commented. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] timeSeries featureType with a forecast / reference time dimension? (#129)
Thanks, Jonathan - The PR looks fine to me. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/129*issuecomment-1006674737__;Iw!!G2kpM7uM-TzIFchu!mM-appc03Ubz8M9PvykkgU8ouKliPAF90XIprzDM4jEuHLYd0oka5-U8ZwkHeQaT2D4dn6lzvBM$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] timeSeries featureType with a forecast / reference time dimension? (#129)
Thanks -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/129*issuecomment-1006663320__;Iw!!G2kpM7uM-TzIFchu!inhZSwNqcSngidTPij8gVZ1YpNxYhO5xE3JBYPtrTLoXrxpCrW89S7d3dLzvQakqCJ5qOTWe5FY$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] timeSeries featureType with a forecast / reference time dimension? (#129)
Thanks @JonathanGregory . If you have no objections, I'll set a reminder to myself to merge this in 3 weeks (2022-01-27) so that interested parties can comment on the small modifications to the updated draft in good time. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/129*issuecomment-1006651985__;Iw!!G2kpM7uM-TzIFchu!nPyHvLUeYwbG4LjBnFTi_m_GZ--4WbhPR0vsRnNaXXhZFGhwWSBDfL5zdfkFhfgQXopdFwj7QGY$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] Cutting version 1.10 (Issue #345)
@JonathanGregory I agree that a per-release entry in History would make sense. What you propose regarding labels would work, although it might be simpler if we track them by pull requests. This is a common pattern in the software development world. This has been made easy for 1.9 as shown by [this filter](https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pulls?q=is*3Apr*is*3Aclosed*sort*3Aupdated-desc*milestone*3A1.9__;JSslKyUrJQ!!G2kpM7uM-TzIFchu!ivMSC2HJq-YCLwK0BeitySBXv3CAIO1p9skWWONzVAEI2DPu_4Wcznuylq7VMXtvkx341r-KSb4$ ) showing those PRs that were manually tagged as going into 1.9. If we were to do that again for 1.10 we would have such an overview, and the PRs would of course link back to their respective issues. Barring that, this can be discovered by pulling up closed PRs and sorting by date, then checking what was merged into `main` between releases - that is however more laborious, so labeling the PRs pre-merge would be the most expedient in my view. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/345*issuecomment-1006644633__;Iw!!G2kpM7uM-TzIFchu!ivMSC2HJq-YCLwK0BeitySBXv3CAIO1p9skWWONzVAEI2DPu_4Wcznuylq7VMXtvkx345Y6bHxM$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] Single-source the version number (Issue #343)
Personally, I'm more for the terser formulation of `draft` - IMO that makes it obvious enough. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/343*issuecomment-1006643482__;Iw!!G2kpM7uM-TzIFchu!jCiP3-VMGr2lbbobclyJ0fNi0G71NYMNysLZr1jZuNlc_B2U21ruK6EUOOqEeh6EpRGqEFQ-7aM$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] timeSeries featureType with a forecast / reference time dimension? (#129)
The PR is https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/346__;!!G2kpM7uM-TzIFchu!l4h76Wxxnb3d7vg0CfHEc_Q6ifhKedEAAGxCk42s6xr2QZgkgpdY8Q1s7upJsWX9bde5KuXOMKE$ -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/129*issuecomment-1006619988__;Iw!!G2kpM7uM-TzIFchu!l4h76Wxxnb3d7vg0CfHEc_Q6ifhKedEAAGxCk42s6xr2QZgkgpdY8Q1s7upJsWX9bde5Xkr1z-c$ You are receiving this because you are subscribed to this thread. Message ID: 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.
[CF-metadata] [cf-convention/cf-conventions] Issue129 (PR #346)
See issue #129 for discussion of these changes. - [N/A] Authors updated in `cf-conventions.adoc`? - [N/A] Next version in `cf-conventions.adoc` up to date? Versioning inspired by [SemVer](https://urldefense.us/v3/__https://semver.org__;!!G2kpM7uM-TzIFchu!lMzi2aHz0VCCXwrAg54pJgV_UzX353dWcByCAjfiNNPzAlObqSCSrQ_UI-w65t4V_8xYDdkfO5E$ ). - [Y] `history.adoc` up to date? - [N/A] Conformance document up-to-date? You can view, comment on, or merge this pull request online at: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/346__;!!G2kpM7uM-TzIFchu!lMzi2aHz0VCCXwrAg54pJgV_UzX353dWcByCAjfiNNPzAlObqSCSrQ_UI-w65t4V_8xYfb3aAw0$ -- Commit Summary -- * corrected issue 129 * updated history -- File Changes -- M ch09.adoc (4) M history.adoc (3) -- Patch Links -- https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/346.patch__;!!G2kpM7uM-TzIFchu!lMzi2aHz0VCCXwrAg54pJgV_UzX353dWcByCAjfiNNPzAlObqSCSrQ_UI-w65t4V_8xYa0L3WBk$ https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/346.diff__;!!G2kpM7uM-TzIFchu!lMzi2aHz0VCCXwrAg54pJgV_UzX353dWcByCAjfiNNPzAlObqSCSrQ_UI-w65t4V_8xYoXt5nqM$ -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/346__;!!G2kpM7uM-TzIFchu!lMzi2aHz0VCCXwrAg54pJgV_UzX353dWcByCAjfiNNPzAlObqSCSrQ_UI-w65t4V_8xYfb3aAw0$ You are receiving this because you are subscribed to this thread. Message ID: cf-convention/cf-conventions/pull/3...@github.com 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.
Re: [CF-metadata] [cf-convention/cf-conventions] Single-source the version number (Issue #343)
I agree with putting `draft` in the current-version. I think it would be a positive advantage if it turns up e.g. in `Conventions` (in the text of the draft document), because that makes the status obvious. In fact maybe we could be more explicit and say e.g. `:current-version: 1.10 draft (not yet released, not to be used)` or is that going too far? -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/343*issuecomment-1006601253__;Iw!!G2kpM7uM-TzIFchu!gmDvuWnAHhcNEbiLrMd_YpBiOLpsaphXSMZLtQvPAfGl-qgZxQwkB48attuVS-y0Tyc0w65NRE0$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] Single-source the version number (Issue #343)
@JonathanGregory thanks for bringing us back on track! > Might it make sense to do this?: > > :current-version: 1.10 draft > > And then remove draft pre-release? I think that would make sense. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/343*issuecomment-1006599840__;Iw!!G2kpM7uM-TzIFchu!jttTw2yUABTJgBdvfkzErMN9qDha-JO5EuRaIAReK6afQ4WKG02j12gvIEfQtYqQ9Y0A9UalC7s$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] Single-source the version number (Issue #343)
Discussion in review comments of https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/344__;!!G2kpM7uM-TzIFchu!lLnLFd19gThcoMUaRLU_pBH4VxrLNZCKKoySzJQnQfoNQoRM5jsViIxya-aghDFqq-QhUmVjGFI$ reproduced here for the record. (May I politely and respectfully remind everyone that the CF practice is to keep substantive discussions about text in the issue, not the PR, so we have a single place to look for the history. Thanks. :smile: ) @erget: Might it make sense to do this?: `:current-version: 1.10 draft` And then remove ` draft` pre-release? @zklaus: I had this locally at some point, but I removed it again because I felt that it looked odd in the `:Conventions` attribute both in the examples, which would read ``` // global attributes: :Conventions = "CF-1.10 draft" ; :featureType = "timeSeries" ; ``` and in the text where this attribute is described, for example ``` [...] attribute **`Conventions`** to a string value that contains "**`CF-1.10 draft`**". ``` Hence my suggestion to add a second `:status-indicator:` or similar that can be combined with the `:current-version:` where appropriate. But I am happy to use the simpler solution :) @erget: I don't have overly strong feelings here, but in the absence of Sturm und Drang from other corners my preference would be to go with using `current-version` for the whole shebang. Reasoning: - It's simpler than having 2 attributes - It doesn't result in invalid CDL, since space characters are allowed and thus it would be easier to maintain, and also more obvious that one is working with a draft. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/343*issuecomment-1006598333__;Iw!!G2kpM7uM-TzIFchu!lLnLFd19gThcoMUaRLU_pBH4VxrLNZCKKoySzJQnQfoNQoRM5jsViIxya-aghDFqq-QhhTqL448$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] Cutting version 1.10 (Issue #345)
Separately, I would like to suggest that when we close issues in this repository which have been agreed to be implemented in the next release, we should add another label that indicates this e.g. "1.9" for all the ones added to the present version. Those new labels can all be the same colour, to conserve the visual spectrum. I think these labels might be useful when looking at the repo subsequently. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/345*issuecomment-1006593459__;Iw!!G2kpM7uM-TzIFchu!mjoq12mBpBMW03dfJZ39AaDXxG2Sk-mQb3g7FpDq0OAecBdvP9tL0v74L87yeEQnWsGLPoA4rsE$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] Cutting version 1.10 (Issue #345)
We could put headings in the history section (in `history.adoc`), starting a new one in each new release. Thus, the history section in the present draft would begin with a title something like "Differences between 1.9 and 1.10", and there would be nothing there. Just to be clear, we could write "Nothing yet" underneath, and delete it in the subsequent changes! Does that make sense? -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/345*issuecomment-1006591458__;Iw!!G2kpM7uM-TzIFchu!llifoEiYRK0xT7lJ2e_wleg1MDNaRcWnXiNbhChbguJUlZ7cvho0nYTSt2KVAVjmLh7L3vEhZVA$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] DOIs for CF Convention releases? (#127)
@castelao : I like the idea of having a DOI for the CF concept, but I would like to take this opportunity to clarifying what that concept is. @ethanrd has suggested, I think, that the concept can be defined, in effect, by pointing to cfconventions.org, but I feel it would be more in the spirit of the DOI culture to have a specific, very short and durable, text that defines the concept, such as the first paragraph on the home page. With this approach, the link to cfconventions.org would be metadata, and could be updated at will on Zenodo or any other platform. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/127*issuecomment-1006452099__;Iw!!G2kpM7uM-TzIFchu!gkPa7iEXPxgwfwpxvJm1elpr0R2_OMqrcHjzrD8db4SSdc0uCo_Y-5jPcE4fXV_DVFsa0zPUot0$ You are receiving this because you commented. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] Cutting version 1.10 (Issue #345)
@davidhassell ping - thoughts here? (1) is a very good question - is there an easy way to generate such an overview in the absence of updates to the history section of the document? I imagine GitHub would be helpful, and it might be even easier if we use milestones that could be attached to PRs but AFAIK we're not doing that. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/345*issuecomment-1006423070__;Iw!!G2kpM7uM-TzIFchu!nPUC0VMZ9Y8l7dT2INGIm5AClqwSFRGhh1sse06g2VioOaWeo2PqABo4SCiXhG5xTn_r2ZUFeo4$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] Single source version (PR #344)
@erget commented on this pull request. > @@ -0,0 +1 @@ +:current-version: 1.10 I don't have overly strong feelings here, but in the absence of Sturm und Drang from other corners my preference would be to go with using `current-version` for the whole shebang. Reasoning: - It's simpler than having 2 attributes - It doesn't result in invalid CDL, since space characters are allowed and thus it would be easier to maintain, and also more obvious that one is working with a draft. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/344*discussion_r779423131__;Iw!!G2kpM7uM-TzIFchu!i-lLctLOpkeIGqFCsuJ5EX69WCWBhTW8-cqMiqoZUWfWft6oqoeco78uTHWL--XgZrdOCLiAhys$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] timeSeries featureType with a forecast / reference time dimension? (#129)
Aha! Quite right. I did only half the job. :-) I will write the PR. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/129*issuecomment-1006412636__;Iw!!G2kpM7uM-TzIFchu!hDHDso0W7V7kzKHW3jTFG3KkGcvTEIOOxGWlhN9BVgiTSWhsgh2dyxu2NKVZK1eLAKRptjzOMKA$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] timeSeries featureType with a forecast / reference time dimension? (#129)
@JonathanGregory which PR is associated with this issue? I don't see one linked. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/129*issuecomment-1006405116__;Iw!!G2kpM7uM-TzIFchu!nvigjS3Km1-BYHgyTIi_6s5aK87qD9kjRwPE5hRen0XwMljN2_ACW7iKFGzSg7DqPwXHsa4fJco$ You are receiving this because you are subscribed to this thread. Message ID: 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.
Re: [CF-metadata] [cf-convention/cf-conventions] timeSeries featureType with a forecast / reference time dimension? (#129)
Please could someone merge this pull request, which qualifies for acceptance today. Thanks. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/129*issuecomment-1006394416__;Iw!!G2kpM7uM-TzIFchu!mvI4nlPo6xsIV8bPj7RF_KY_Vhk_EEMymi_EZL_z1zu9HlIufrvze6EKnRqDhm12fIeit5JIgsk$ You are receiving this because you are subscribed to this thread. Message ID: 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.
