Changes between Version 8 and Version 9 of CMDI 1.2/Rollout

Timestamp:

06/09/16 07:14:32 (8 years ago)

Author:

Twan Goosen

Comment:

--

CMDI 1.2/Rollout

@@ -25 +25 @@
 * [] Run a 'dry' [#Componentconversion component conversion] on a dump of the Component Registry database to see if there are no new problematic cases
 * [] Stop the Component Registry
-* [] [#Componentconversion Convert] of all component and profile definitions within the Component Registry with the component upgrade tool
+* [#Componentconversion Convert] of all component and profile definitions within the Component Registry with the component upgrade tool:
+ * [] Backup the Component Registry database
+ * [] Run the upgrade tool (see below for details) and make sure that it terminates without any errors
+  * in case of errors, most likely one or more components need to be fixed
+ * [] Make a backup of the freshly converted database
 * [] Deploy and start the Component Registry version with support for CMDI 1.2
 
@@ -37 +41 @@
 
 A utility called the [https://github.com/clarin-eric/component-registry-rest/tree/develop/ComponentUpdater ComponentUpdater] applies the upgrade stylesheet to all components in the Component Registry database and validates the output. If all components transform and validate successfully, it commits the changes.
+
+A prepared (compiled and pre-configured) package will be made available to run on production at the time of rollout of CMDI 1.2.
 
 === Problematic components ===