@@ -46,20 +46,17 @@ are defined in the :doc:`README`.
46
46
47
47
We follow `semantic versioning `_, but drop the bug fix level version number for
48
48
our images, as this level of granularity is not important for any application of
49
- these images. Each release is tagged in Git, and the release version number is
50
- included in the Dockerfile version label (``LABEL version="2.0" ``).
49
+ these images.
51
50
52
51
Releases should be merged into one of the ``releases/ `` branches, for instance
53
- ``releases/2.x ``. The version label in the Dockerfile should be updated to the
54
- next version in the series, following semver rules. This commit should then also
55
- be tagged using the new version number.
52
+ ``releases/2.x ``. This commit should then also be tagged using the new version number.
56
53
57
- If the version number in the Dockerfile was ``2.0.1 `` before, and you implement
54
+ If the version number was ``2.0.1 `` before, and you implement
58
55
a bug fix to the image, the new image will be ``2.0.2 ``. The output image from
59
56
Docker Hub will still be ``2.0 `` however. If a new feature is introduced, the
60
- new version tagged and in the Dockerfile will be ``2.1 ``.
57
+ new version tagged will be ``2.1 ``.
61
58
62
- We don't care about bug fix version numbers here, as RTD will only ever have one
59
+ We don't care about bug fix version numbers here, as Read the Docs will only ever have one
63
60
main ``2.x `` image at a time. There is no need for us to run multiple bug fix
64
61
versions at the same time.
65
62
0 commit comments