Changes between Version 2 and Version 3 of CMDI 1.2/Schema version management


Ignore:
Timestamp:
10/25/13 13:59:22 (11 years ago)
Author:
twagoo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • CMDI 1.2/Schema version management

    v2 v3  
    1111== Proposed solution ==
    1212
    13 === Source repository structure and publication ===
    14 
    15 * Current [source:/metadata/trunk/ trunk] will be branched of to [source:/metadata/branches/cmdi-1.1 branches/cmdi-1.1]
    16 * [source:/metadata/trunk/ trunk] will be used for development of CMDI 1.2 with 'snapshot' status
    17 * changes found to be stable get merged to a branch [source:/metadata/branches/cmdi-1.2 branches/cmdi-1.2]
    18 * Cronjob on infra.clarin.eu gets adapted to check out both branches to [http://infra.clarin.eu/cmd/1.1] and [http://infra.clarin.eu/cmd/1.2] respectively
     13* The current [source:/metadata/trunk/ trunk] will be branched of to [source:/metadata/branches/cmdi-1.1 branches/cmdi-1.1]
     14* The [source:/metadata/trunk/ trunk] will then be used for development of CMDI 1.2 with 'snapshot' status
     15* Changes found to be stable get merged to a branch [source:/metadata/branches/cmdi-1.2 branches/cmdi-1.2]
     16* The cronjob on infra.clarin.eu gets adapted to check out both branches to [http://infra.clarin.eu/cmd/1.1] and [http://infra.clarin.eu/cmd/1.2] respectively
    1917* The location [http://infra.clarin.eu/cmd] will be configured to redirect (301) to [http://infra.clarin.eu/cmd/1.1] so as not to break compatibility with the existing infrastructure
    20 
    21 === Version specification in components ===
    22 
    23 TODO
     18* Tags can optionally be created for significant changes within minor versions for future reference
     19 * Possibly keep an internal 'maintenance' release version (added 3rd level) for this or use some other property (date or svn revision)
    2420
    2521==== Pros ====
    … …  
    2723* Centralised development with versioning possible without the risk of altering production
    2824* Allows for parallel development of 1.2 and maintenance (such as emergency fixes) of 1.1
     25* The CMDI version can be derived from the schema location in a component specification (e.g. http://infra.clarin.eu/cmd/1.2/general-component-schema)
    2926
    3027==== Cons ====
    3128
    32 Cons of this solution
     29* Releases are still pulled from svn and not pushed (as with maven artifacts). Convenient but not so tidy.
    3330
    3431==== Centre impact ====
    3532
    36 * Affected tools
    37 * Impact on instances
     33* Component Registry has to change its referred schema and stylesheet locations
     34* ems04 (hosting infra.clarin.eu) needs to have its cronjob updated
    3835
    3936== Tickets ==