Update Help for release actions authored by Julien Osman's avatar Julien Osman
......@@ -55,19 +55,15 @@ For convenience, nightly generated source packages should be available
For more information, check the script `OTB/CI/deploy.sh`, and the command `git archive`.
You will have to copy and rename the release archives into `/var/www/archives/packages/archives/OTB`. Then, create a symbolic link in `/var/www/archives/packages`
You will have to copy and rename the release archives into `/var/www/archives/packages/archives/OTB`. This directory stores all the released versions of OTB.
Then, create a symbolic link in `/var/www/archives/packages`. This directory contains links to the current release of OTB. This means you should remove older links from this directory.
For a release version 3.2.1, the naming convention should follow the
pattern `OTB-3.2.1.[zip/tar.gz/tar.xz]`.
If it is the 2nd release candidate: `OTB-3.2.1-rc2.[zip/tar.gz/tar.xz]`.
The management of older versions is done during the release process, so
that at each time there is at least one stable release (non RC) in the
packages directory. Older versions remain archived in:
/var/www/archives/packages/archives
## Update the RELEASE_NOTES.txt
As proposed [here](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/1953#note_80787).
......
......