Changes between Version 2 and Version 3 of BonminBranches


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

Put some bold remove some version number

Legend:

Unmodified
Added
Removed
Modified
  • BonminBranches

    v2 v3  
    1  * In the Stable branch, are version of the code which are distiguished by two digits release numbers. The current '''latest stable version is 0.1'''. They are stable in the sense that:
     1 * In the Stable branch, are version of the code which are distiguished by two digits release numbers. They are stable in the sense that:
    22   * They have been tested on a relatively large test set of problem.
    33   * They may evolve in time as bug are found and corrected.
    44   * Although bug fixes are applied, for given stable version (say 0.1), updates should not change the usage and the API.modified.
    5    * They rely on external COIN-OR projects which are also stable and should have the same properties.
     5   * If change are made to the code which change its usage or the API, a stable with a new version number is created.
     6   * They rely on '''stable external COIN-OR projects''' (which should obey the same rules).
    67   
    78   A Stable version of Bonmin can only be obtained using subversion (and can be easily updated to included the latest bug-fixes by using the command svn update.
    89
    9  * In the released branch, versions of the codes are distinguished by three digits release numbers. The '''latest released version is 0.1.1'''. The released version have the following properties.
     10 * In the released branch, versions of the codes are distinguished by three digits release numbers. The released version have the following properties.
    1011   * They have been tested on a relatively large test set of problem.
    11    * 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).
    12    * They rely on external COIN-OR projects which are also releases and should have the same properties.
     12   * 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).
     13   * They rely on '''released external COIN-OR projects''' (which should obey the same rules).
    1314
    1415   Released version are for example advisable to use if you want to make experimental tests which you want to be reproducible over time, Released versions can be downloaded either with subversion or as a tarball.
    1516
    1617
    17   * 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.
     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.
    1819
    1920