Changes between Version 3 and Version 4 of BonminBranches


Ignore:
Timestamp:
Oct 27, 2006 1:11:16 PM (13 years ago)
Author:
pbonami
Comment:

Even bolder

Legend:

Unmodified
Added
Removed
Modified
  • BonminBranches

    v3 v4  
    11 * In the Stable branch, are version of the code which are distiguished by two digits release numbers. They are stable in the sense that:
    2    * They have been tested on a relatively large test set of problem.
    3    * They may evolve in time as bug are found and corrected.
    4    * Although bug fixes are applied, for given stable version (say 0.1), updates should not change the usage and the API.modified.
     2   * They have been '''tested''' on a relatively large test set of problem.
     3   * They may '''evolve in time''' as bug are found and corrected.
     4   * The '''usage and API do not change'''. Although bug fixes are applied, for a given stable version number (say 0.1), updates should not change the usage and the API.modified.
    55   * If change are made to the code which change its usage or the API, a stable with a new version number is created.
    66   * They rely on '''stable external COIN-OR projects''' (which should obey the same rules).
     
    99
    1010 * In the released branch, versions of the codes are distinguished by three digits release numbers. The released version have the following properties.
    11    * They have been tested on a relatively large test set of problem.
     11   * They have been '''tested''' on a relatively large test set of problem.
    1212   * They '''never change'''. If a bug fix is applied a new release with a different version number may be created but in no case release 0.1.1 will change).
    1313   * They rely on '''released external COIN-OR projects''' (which should obey the same rules).
     
    1616
    1717
    18   * In the developement branch, there is no versionning number. The code in the development branch should be considered unstable and can change from one day to another. The code depends on other COIN-OR projects which are also under development. Although we usually try to resolve it when it happens, it may be that the code in the development branch is incompatible with the latest development in other projects. The development branch is the source for the forthcoming stable and releases.
     18  * In the developement branch, there is no versionning number. The code in the development branch should be considered:
     19    * '''unstable'''
     20    * '''Usage and API and can change''' from one day to another.
     21    * The code '''rely on unstable external COIN-OR projects'''. Although we usually try to resolve it when it happens, it may be that the code in the development branch is incompatible with the latest development in other projects.
     22    * The development branch is the source for the forthcoming stable and releases.
     23    The development branch is downloaded by svn it can be found in branches/devel in the svn tree.
    1924
    2025