This page is a subpage of CMDI 1.2

Schema version management

The issue

Currently the CMDI 'toolkit' (general component schema, component-to-schema stylesheet and related resources) is being developed and released from the trunk. The trunk version of these documents is checked out on the ​production server and gets updated through a cron job. This makes testing a hassle and proper versioning impossible. Since we should keep 1.1 maintainable even after the release of 1.2, a better structure is desirable.

Proposed solution

• The current trunk will be branched off to branches/cmdi-1.1
• The trunk will then be used for development of CMDI 1.2 with 'snapshot' status
• Changes found to be stable get merged to a branch branches/cmdi-1.2
• 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
• 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
• Tags can optionally be created for significant changes within minor versions for future reference
  • Possibly keep an internal 'maintenance' release version (added 3rd level) for this or use some other property (date or svn revision)

Pros

• Centralised development with versioning possible without the risk of altering production
• Allows for parallel development of 1.2 and maintenance (such as emergency fixes) of 1.1
• The CMDI version can be derived from the schema location (e.g. ​http://infra.clarin.eu/cmd/1.2/general-component-schema) in a component specification

Cons

• Releases are still pulled from svn and not pushed (as with maven artifacts). Convenient but not so tidy.

Centre impact

• Component Registry has to change its referred schema and stylesheet locations
• ems04 (hosting infra.clarin.eu) needs to have its cronjob updated

Tickets

Tickets in the CMDI 1.2 milestone with the keyword schemaversion:

Ticket	Summary	Owner	Component	Priority	Status
No tickets found

Discussion

Discuss schema version management below this point