... | ... | @@ -182,3 +182,14 @@ For example: version `2020.1.0` is the first major release (without revision) in |
|
|
|
|
|
The DAU project [silx](https://www.silx.org) uses a "fixed release rate" (every 3 or 6 months).
|
|
|
Nabu releases are done according to a [roadmap](https://tomotools.gitlab-pages.esrf.fr/tomo-bridge-docs/data-proc/roadmap), which can include intermediate releases. Therefore, there is no "fixed release rate", although we tend to make at least one major release every 3 months.
|
|
|
|
|
|
### 6.4 - Definition in the code
|
|
|
|
|
|
The nabu version is defined in one unique place: `nabu/__init__.py`.
|
|
|
|
|
|
We do not use "modifiers" (ex. "dev", "alpha", ...), except for release candidates. This means that versions usually look like `__version__ = "2020.3.0"`, or `__version__ = "2020.3.0-rc1"` (release candidate 1).
|
|
|
|
|
|
This means that once a new version is released (ex. `2020.3.0`), the revision (number `Z`) is immediately incremented in `nabu/__init__.py` (ex. `2020.3.1`).
|
|
|
For example, installing version `2020.3.0` from pypi provides this final (major) release ; and an installation from gitlab will provide version `2020.3.1` (more recent but not released).
|
|
|
|
|
|
Installations from gitlab should always be considered as a development versions, except if the commit corresponds to a tagged release. |
|
|
\ No newline at end of file |