|
|
|
@ -120,13 +120,14 @@ how to use cdist. |
|
|
|
|
There are at least the following branches available: |
|
|
|
|
|
|
|
|
|
* master: the development branch |
|
|
|
|
* 1.3: Support for local and remote code execution (current stable) |
|
|
|
|
* 1.4: Support for redefiniton of objects (if equal) |
|
|
|
|
|
|
|
|
|
Old versions: |
|
|
|
|
|
|
|
|
|
* 1.0: First official release |
|
|
|
|
* 1.1: __file to __file, __directory, __link migration |
|
|
|
|
* 1.3: Support for local and remote code execution (current stable) |
|
|
|
|
* 1.2: Dependencies supported |
|
|
|
|
* 1.1: __file to __file, __directory, __link migration |
|
|
|
|
* 1.0: First official release |
|
|
|
|
|
|
|
|
|
Other branches may be available for features or bugfixes, but they |
|
|
|
|
may vanish at any point. To select a specific branch use |
|
|
|
@ -156,6 +157,10 @@ If you stay on a version branche (i.e. 1.0, 1.1., ...), nothing should break. |
|
|
|
|
The master branch on the other hand is the development branch and may not be |
|
|
|
|
working, break your setup or eat the tree in your garden. |
|
|
|
|
|
|
|
|
|
### Upgrading from 1.3 to 1.4 |
|
|
|
|
|
|
|
|
|
No incompatiblities. |
|
|
|
|
|
|
|
|
|
### Upgrading from 1.2 to 1.3 |
|
|
|
|
|
|
|
|
|
Rename **gencode** of every type to **gencode-remote**. |
|
|
|
|