... | ... | @@ -33,7 +33,7 @@ The day of the release: |
|
|
- push stable to the server, using the `--tags` option to send the tag as well (the tag must be in the repository *before* you attempt to build the Debian packages)
|
|
|
- on branch, `master`, add `.dev` the the version number, update `NEWS` for this version, merge `master` into `next`, and push both `master` and `next`.
|
|
|
- jump to the pipelines for spot, and cancel the duplicate pipeline for `master`, keeping only `stable` and `next`
|
|
|
- while waiting for the `stable` pipeline [![stable status](https://gitlab.lrde.epita.fr/spot/spot/badges/next/pipeline.svg)](https://gitlab.lrde.epita.fr/spot/spot/commits/stable) and the `next` [![next status](https://gitlab.lrde.epita.fr/spot/spot/badges/next/pipeline.svg)](https://gitlab.lrde.epita.fr/spot/spot/commits/next) pipeline to finish, prepare the announcement mail for spot-announce
|
|
|
- while waiting for the `stable` pipeline [![stable status](https://gitlab.lrde.epita.fr/spot/spot/badges/stable/pipeline.svg)](https://gitlab.lrde.epita.fr/spot/spot/commits/stable) and the `next` [![next status](https://gitlab.lrde.epita.fr/spot/spot/badges/next/pipeline.svg)](https://gitlab.lrde.epita.fr/spot/spot/commits/next) pipeline to finish, prepare the announcement mail for spot-announce
|
|
|
- both the `stable` and `next` pipelines will trigger builds of `spot-web` project, but one build will create the main website, and the other will create the development one. The `next` pipeline also trigger a build of the `spot-sandbox` image. All those web containers are simply pushed to our docker registry, and they get deployed by a crontab that runs at xx:20 every hour.
|
|
|
- once the new web server is running well, send the announcement email
|
|
|
- add `.dev` to the version number in `configure.ac`, and add an empty entry at the top of `NEWS` with this version number
|
... | ... | |