Changes between Version 4 and Version 5 of Taskforces/CMDI/Meeting20160810


Ignore:
Timestamp:
08/09/16 11:38:16 (8 years ago)
Author:
Twan Goosen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Taskforces/CMDI/Meeting20160810

    v4 v5  
    3030  * Element with only an enum was not handled correctly and !ValueScheme patterns were lost, both in 'comp2schema' transformation - fixed
    3131  * Registering new components in the component registry did not work due to bad initialisation, this was fixed in Component Registry 2.1.1 (some days after the 2.1.0 deployment)
    32  * Some issues related to component downgrade that surfaced very recently have been fixed in a maintenance release of the toolkit, [https://github.com/clarin-eric/cmdi-toolkit/releases/tag/cmdi-1.2.1 version 1.2.1]
     32 * Some issues related to component downgrade that surfaced very recently have been fixed in a maintenance release of the toolkit, [https://github.com/clarin-eric/cmdi-toolkit/releases/tag/cmdi-1.2.1 version 1.2.1], used by [https://github.com/clarin-eric/component-registry-rest/releases/tag/ComponentRegistry-2.1.3 Component Registry 2.1.3]