Changes between Version 14 and Version 15 of RasdamanReleaseProcess


Ignore:
Timestamp:
May 22, 2013, 10:38:18 AM (12 years ago)
Author:
Dimitar Misev
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • RasdamanReleaseProcess

    v14 v15  
    1515A single main repository is maintained (as we already have).
    1616
    17 The repository contains two types of ''branches'' on it:
     17The repository contains three types of ''branches'' on it:
    1818 * '''master''' (single instance) -- the currently available branch, which will be the main development branch;
    1919 * '''release''' (multiple instances) -- When starting release process (consolidation of beta, rc, and other testing releases), a ''release'' branch is created with name '''release_M.m'''. These branches will allow maintenance of past releases, while development continues in the master branch.
    2020  * Where M=Major version; m=minor version; All patch versions will belong to the same "minor" branch
    2121   * Note: consider broader detail such as per-major version release line (fewer branches) or cleaning up branches for un-maintained versions
     22 * '''feature''' (multiple instances) -- Indicating a branch where a new feature is developed. This is kept in a branch separate from the others, as developing new features results in unstable code.
     23  * Feature branches are named '''feature_M.m-FeatureName''', e.g. `feature_9.0-PetascopeNewSchema`
    2224
    2325As an example consider release 8.4.0 and following bugfixes and regression patches: