... | @@ -18,7 +18,6 @@ A couple of days before the release: |
... | @@ -18,7 +18,6 @@ A couple of days before the release: |
|
- Make sure `master` (if maintenance release) or `next` (if major release) has all the patches you want to release.
|
|
- Make sure `master` (if maintenance release) or `next` (if major release) has all the patches you want to release.
|
|
- Check locally that the online translator page in `wrap/python/ajax/` is still working: it's not part of the test suite, but it will be installed on the web server.
|
|
- Check locally that the online translator page in `wrap/python/ajax/` is still working: it's not part of the test suite, but it will be installed on the web server.
|
|
- Check that the [third-party tools](https://github.com/adl/spot-docker/blob/master/debuild/install.sh) installed in the docker containers are up-to-date.
|
|
- Check that the [third-party tools](https://github.com/adl/spot-docker/blob/master/debuild/install.sh) installed in the docker containers are up-to-date.
|
|
- Rebuild the docker containers ([gadl/spot-debuild](https://hub.docker.com/r/gadl/spot-debuild/) & [gadl/spot-debuild-i386](https://hub.docker.com/r/gadl/spot-debuild-i386/)) by triggering new builds on dockerhub. This will ensure that our Debian packages are built against the most recent version of all the other Debian packages they depend upon.
|
|
|
|
- Make sure `master` and `next` compile with the new container for unstable (this is done every night after a new commit on `next`)
|
|
- Make sure `master` and `next` compile with the new container for unstable (this is done every night after a new commit on `next`)
|
|
- Make sure `master` and `next` compile with the new container for stable (you need to trigger this build by hand)
|
|
- Make sure `master` and `next` compile with the new container for stable (you need to trigger this build by hand)
|
|
|
|
|
... | | ... | |