OHDSI Home | Forums | Wiki | Github

CDM Versioning and Github Clean-up

Hi Everyone:

There have been some questions around the current CDM version, when versions will be released and what is currently going on in the github (specifically issues #56 and #44).

Right now the most current release of the CDM on the github is v5.0.1, the master branch is v5.1.0, set to be released by the end of this week, there is a branch v5.1.1 with a bug fix and in the CDM workgroup we are discussing and adding to v5.2.0. I am keeping these versions separate rather than merging everything into v5.2.0 because @cukarthik and others are using v5.1.0 in their research and it would cause problems if we skipped straight to v5.2.0.

My current task is to reconcile these versions so that we can be completely caught up with v5.2.0 and as we continue to move forward with new proposals I am going to make sure they are added in a timely manner to both the DDL and documentation. As part of this effort I am moving all of the documentation of the CDM that is currently housed on the wiki and moving it to github to manage as changes to the CDM are ratified. In the new system the wiki will show only the most recent release and the github will house all of the documentation for previous versions.

Part of this new system will also be a change to the way proposals are handled, each one will become a github issue so that they can be tracked and closed as a new version is released.

I would also like to change the release schedule, I would like to aim to release a minor version (e.g., 5.2.0) every quarter and a major version (e.g., 6.0.0) at the beginning of the year with micro versions for bug fixes released as needed. This would mean 5.2.0 would be released on 7/1/2017. This is a little tight considering the work that needs to be done so in the event it is released after 7/1 we will aim to be on schedule with v5.3.0 on 9/1/2017.

@Rijnbeek, I hope this answers your questions and if would like to add your DDLs to a v5.2.0 branch, please feel free. I will merge your changes once I release v5.1.1.

Thanks,
Clair

2 Likes

Thanks Clair for clarifying.

Verstuurd vanaf mijn iPhone

This is good clarification.

I would like to suggest that given community effort, it is hard to add changes to all supported SQL flavors for every release.

Perhaps an approach where as volunteers contribute changes, we may release 5.2 or 5.1 with not all flavors included. (perhaps one missing out of 4 out there)

E.g., Oracle DDL may be missing from 5.2 (since no Oracle-using volunteer contributed the labor to do it). (and some volunteers simply don’t have all possible servers to test it).

Why don’t we ask them? It’s easy after all. Just run the DDL and see what happens.

t