Need a versioning system

[climbfuji]

It was brought up not only recently that we need a versioning system for the CCPP standard names.

My immediate reaction is that this can be done in form of coding the version in the XML file and creating corresponding git tags.

[mkavulich]

@climbfuji Thanks for opening this issue. Including a version number in the XML was my first thought as well. This does bring up the question of how we would go about incrementing version numbers. Though more importantly, there is no current method of "enforcing" standard names compliance (as evidenced by the fact that the ccpp-physics repository is far out of compliance with the current set of names), so any versioning would have to be considered in that context as well. Probably worth a discussion item at the next meeting.

[svahl991]

I'm not sure how often you meet, or if this was discussed, but I'm curious if there's any update on this issue.

[svahl991]

Has there been any movement or further discussion on this issue?

[shlyaeva]

Checking in whether there has been progress on versioning. With JEDI adopting CCPP more across the code base, and with occasional name changes in CCPP it is important for us to have tags of CCPPStandardNames, so we can update the JEDI code base to the changes in CCPP names with some regularity (instead of trying to keep up with develop).

[climbfuji]

How about we target a tag after the currently open PRs (and others from your code sprint) are merged/addressed/resolved so that you have a version to reference for skylab v9?

[shlyaeva]

I think we may want a few more names before tagging: we are planning a code sprint for the week of October 7th and there are a few more names that we would like to address during that sprint. We'll issue PRs within this and next week; we'll ping in this issue once all PRs are submitted.