kombu icon indicating copy to clipboard operation
kombu copied to clipboard

Order of the release tags is broken

Open matusvalo opened this issue 4 years ago • 2 comments

Since version of kombu 4.5.0 the tag naming convention is changed which broke ordering of releases:

$ git tag -l | head -n 20
4.6.0
4.6.1
4.6.2
4.6.3
4.6.4
4.6.5
4.6.6
4.6.7
4.6.8
v0.1.0
v0.2.0
v0.9.1
v0.9.5
v0.9.6
v0.9.7
v1.0.0
v1.0.0b1
v1.0.0b2
v1.0.0b3
v1.0.0b4

It can be easilly seen that current versions in the beginning This is breaking among other things also documentation where on the read the docs where the latest stable version is still 4.5.0... (due this version is last tag):

image

@auvipy please when releasing keep naming convention of tag name beginning with "v".

matusvalo avatar Jun 01 '20 19:06 matusvalo

got it. will update

auvipy avatar Jun 02 '20 07:06 auvipy

After latest release with tag beginning with "v" documentation is better but still partially broken:

  1. stable is pointing to latest stable version but still there is message pointing to 4.5: image
  2. latest is still pointing to 4.5 release: image

Not sure why this is happening and how this can be fixed. From readthedocs documentation:

In the normal case, the latest version will always point to the most up to date development code. If you develop on a branch that is different than the default for your VCS, you should set the Default Branch to that branch.

You should push a tag for each version of your project. These tags should be numbered in a way that is consistent with semantic versioning. This will map to your stable branch by default.

https://docs.readthedocs.io/en/stable/versions.html

matusvalo avatar Jun 10 '20 08:06 matusvalo