If you're asking whether you should track your i2p-transform and shilhs-ontology changes using git and github, then yes, I highly recommend it. You're more than welcome to fork https://github.com/kumc-bmi/i2p-transform .
Newer versions are typically better than older versions. In particular, for kumc-bmi/i2p-transform, we do new development on branches and only merge reviewed code to master. This is mostly just platitudes; If you can give an example of which CDM v3 fix you have in mind, I might be able to give a more useful answer. -- Dan ________________________________ From: [email protected] [[email protected]] on behalf of Wanta Keith M [[email protected]] Sent: Monday, June 06, 2016 3:02 PM To: [email protected] Subject: CDM v3 Appendix B fixes - pencils down? GPC – Have we make a decision on whether we should be making our CDM v3 Appendix B fixes based on some past revision of the i2p-transform and scilhs-ontology repositories, or…. Should we be applying code changes overtime from GitHub for CDM v3 Appendix B fixes? (putting aside ontology mappings we do internally) Thanks, Keith Wanta (WISC)
_______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev
