Changes between Version 26 and Version 27 of ComponentRegistryAndEditor


Ignore:
Timestamp:
12/18/13 09:23:55 (10 years ago)
Author:
twagoo
Comment:

updated 'Development process' section

Legend:

Unmodified
Added
Removed
Modified
  • ComponentRegistryAndEditor

    v26 v27  
    5454== Development process ==
    5555
    56 * Feature implementations and fixes are assigned to [/roadmap milestones]
    57  * Features are decided on by MPI-PL in consultation with the taskforces (see [http://www.clarin.eu/sites/default/files/cmdi-governance-dvu.pdf this presentation]) and the CLARIN development community (mailing list: [dev@lists.clarin.eu])
    58  * Bugs get reported through [cmdi@clarin.eu] (as mentioned [http://www.clarin.eu/content/component-metadata here])
    59 * Active development happens in [source:ComponentRegistry/trunk trunk]
    60 * As soon as the items on the version milestone have been reached, a branch is created
    61 * The branched version gets deployed to a testing server and is tested internally at MPI-PL (by Corpus Management) according to a test plan
    62 * Once testing has completed successfully, the new version gets deployed to the production server (catalog.clarin.eu, see [[ServerConfig]] for contact information)
     56* '''Feature implementations''' and '''fixes''' are assigned to [/roadmap milestones]; one milestone per minor version
     57 * '''Features''' are decided on by MPI-PL (primary contacts: Daan Broeder, Dieter van Uytvanck) in consultation with the taskforces (see [http://www.clarin.eu/sites/default/files/cmdi-governance-dvu.pdf this presentation]) and the CLARIN development community (mailing list: [mailto:dev@lists.clarin.eu])
     58 * '''Issues''' get reported through [mailto:cmdi@clarin.eu] (as mentioned [http://www.clarin.eu/content/component-metadata here])
     59* Active '''development''' happens in [source:ComponentRegistry/trunk trunk]
     60* As soon as the items on the version milestone have been reached, a '''branch''' is created (e.g. 1.15.0) and minor version number in trunk is bumped
     61* The branched version gets deployed to a '''testing''' server and is tested internally at MPI-PL (by Corpus Management) according to a test plan
     62* Once testing has completed successfully, the new version gets deployed to the '''production''' server (catalog.clarin.eu, see [[ServerConfig]] for info and contacts)
     63* The deployed version gets '''tagged'''
     64* '''Development''' for the next minor version continues in the trunk
     65* '''Maintenance''' releases may be done to the current production branch (leading to e.g. 1.15.1)
    6366
    6467----