Keeping track of the CMOR version about cmor

[doutriaux1]

hi @ehogan the uvcdat-2.4.0 was simply a tag for UV-CDAT since CMOR is distributed as part of UVCDAT we wanted to make sure that user building uvcdat 2.4.0 would always get this version of cmor. @nadeau4 and I will take a look at your issue and make sure it is solved in the upcoming 3.0 release. Thanks!

[ehogan]

That sounds great @doutriaux1, thank you very much! :)

[dnadeau4]

ehogan,

I am working on CMOR 3.0 and I have an alpha release in branch cmor3 due today. You will need to install the json tables found in https://github.com/PCMDI/xml-cmor3-database/tree/master/src and there is a new library called libjson-c that needs to be installed and passed to the configure. I should have more documentation by the end of the day.

Denis

[doutriaux1]

@dnadeau4 let's make sure that her bug is fixed in this release, thanks.

[durack1]

@doutriaux1 @dnadeau4 I think the point raised by @ehogan is a good one.

Why not just tag the CMOR version for the UV-CDAT release with the current CMOR release - so 2.9.3 or 2.9.2 rather than create an arbitrary duplicate tag/release point. The intention is to lock versions, so whether this is a tagpoint named uvdat-2.4.0 or 2.9.2/3 it achieves the same aim

[doutriaux1]

Yes especially since for CMOR master is always the latest stable version. That makes sense.

[durack1]

@doutriaux1 well master keeps moving, 2.9.3 (or similar) shouldn't..

[doutriaux1]

@durack1 yes but I was saying that we don't need a uvcdat specific tag point since uvcdat uses master and master is always at some tag point.

[dnadeau4]

master has now been moved to CMOR 3.1.0