Release 0.38.1
Information about the release
Relevant series
stable
Main reason driving the release
platform stabilisation at Clever and bugfix that did not make it in time for 0.38.0
details
Again a special case: merge already done so we'll skip the topic/MR part and start with the tag step
Task list
-
Omnibus: nothing to be done
-
Rails application
The release branch is e.g.,
heptapod-0-20
while the development branch isheptapod
,heptapod-stable
orheptapod-oldstable
.-
merge stabler development branches into the development branch (pipelines not really needed). -
start from the head of the release branch (e.g, from heptapod-0-20
) -
fill in HEPTAPOD_CHANGELOG 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. -
set HEPTAPOD_VERSION -
commit the changes in version files, push the topic and create a Merge Request targeting the release branch, with automatic merge upon pipeline completion (estimated time between 40 and 90 minutes depending on whether there is a GitLab upstream update) -
create a tag on the release branch head without a topic (run hg topic --clear if needed
before) -
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:
-
take note of the Docker image ID that the heptapod-tests CI jobs ran for -
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 \ --verify-hg-tag heptapod-0.32.1-1 \ --expected-image-id sha256:0e976fdfa6733d4298025cd0b98ae36384863c8dd8d60ac7f9f979bb5d05b259 ```
-
retag the image as as octobus/heptapod:x.y.z
andoctobus/heptapod:latest
oroctobus/heptapod:x-y-latest
, and push the tags to Docker Hub, using thepush-release
script from heptapod/heptapod-docker>.
-
-
Finalisations
-
announce the release at least on Twitter and Mastodon -
publish the changesets in all repositories made during the process (don't forget Omnibus) -
Create group milestone for next point release, move all remaining issues bearing the milestone of this release to it. -
Close milestone for this release.