... | @@ -21,7 +21,15 @@ When we need to tag the global *cameo* project: |
... | @@ -21,7 +21,15 @@ When we need to tag the global *cameo* project: |
|
* **Minor**: Maximum of the current five minor values.
|
|
* **Minor**: Maximum of the current five minor values.
|
|
* **Revision**: Its own revision value that is incremented when a new tag is made with existing major and minor values.
|
|
* **Revision**: Its own revision value that is incremented when a new tag is made with existing major and minor values.
|
|
|
|
|
|
When a version of a project is changed, do not forget to change the corresponding package version in the *CMakeLists.txt* file. The version of the *Cameo* project at the root is not used but should follow the global tag rule.
|
|
### New release
|
|
|
|
|
|
|
|
When making a new release, follow the steps:
|
|
|
|
* Check the package versions in the *CMakeLists.txt* files of the different five projects.
|
|
|
|
* Tag the global project. The version of the *Cameo* project at the root is not used but should follow the global tag rule. Add release notes so that gitlab considers it is a release.
|
|
|
|
* Generate the deb packages using *build_and_package.sh*.
|
|
|
|
* Add the packages in the *releases* directory of the wiki sources of Cameo.
|
|
|
|
* Add the packages as assets in the gitlab edit release page of the version.
|
|
|
|
E.g. for the version 1.1.0, the base link is *https://code.ill.fr/cameo/cameo/-/wikis/releases/1.1.0/*.
|
|
|
|
|
|
|
|
|
|
### Develop on a branch
|
|
### Develop on a branch
|
... | | ... | |