Release 1.5.0
### Information about the release
#### Relevant series
stable
#### Main reason driving the release
Final version. Should be especially simple, as it is expected to be nothing but a rebranding of 1.5.0rc2
### Task list
- [x] Omnibus: no change
- Rails application
The release branch is e.g., `heptapod-0-20` while the development branch
is `heptapod`, `heptapod-stable` or `heptapod-oldstable`.
+ [x] fill in [HEPTAPOD_CHANGELOG](HEPTAPOD_CHANGELOG.md)
Be sure to include the changes related to the stabler branches. If needed
copy them from the stabler *release* branches, as these won't get merged.
+ [x] set HEPTAPOD_VERSION
+ [x] commit the changes in version files
+ [x] create a tag on the release branch head **without a topic** (run
`hg topic --clear if needed` before)
+ [x] push the tag, don't publish it yet. The tag pipeline will push the
source tarball to download.h.n and push a commit to reference it and
a tag in Omnibus. The resulting pipeline in Omnibus will build the
package for Ubuntu, then the Docker image, then trigger a full run
of the functional tests on it, as a pipeline on heptapod-tests.
+ Docker image:
- [x] take note of the Docker image ID that the heptapod-tests CI jobs
ran for
- [x] retrieve the image built in the Omnibus pipeline, checking the
Mercurial tag and the Docker image ID, and push it to Docker Hub,
using the utility in heptapod/heptapod-docker>. Example:
```
~/heptapod/docker $ ./registry-pull-heptapod-push-docker \
--push \
--podman \
--tag 0-32-testing \
--verify-hg-tag heptapod-0.32.1-1 \
--expected-image-id 0e976fdfa6733d4298025cd0b98ae36384863c8dd8d60ac7f9f979bb5d05b259
```
Note: remove `--podman` if you prefer to use Docker instead.
- [x] retag the image as as `octobus/heptapod:x.y.z` and
`octobus/heptapod:latest` or `octobus/heptapod:x-y-latest`, and
push the tags to Docker Hub, using
the `push-release` script from heptapod/heptapod-docker>.
### Finalisations
- [x] announce the release at least on Twitter and Mastodon
- [x] publish the changesets in all repositories made during the process (don't
forget Omnibus)
- [x] Create group milestone for next point release, move all remaining issues
bearing the milestone of this release to it.
- [x] Close milestone for this release.
issue