Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Order of the release tags is broken #1204

Open
matusvalo opened this issue Jun 1, 2020 · 2 comments
Open

Order of the release tags is broken #1204

matusvalo opened this issue Jun 1, 2020 · 2 comments

Comments

@matusvalo
Copy link
Member

matusvalo commented Jun 1, 2020

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".

@auvipy
Copy link
Member

auvipy commented Jun 2, 2020

got it. will update

@auvipy auvipy added this to the 4.6.0 milestone Jun 2, 2020
@matusvalo
Copy link
Member Author

matusvalo commented Jun 10, 2020

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

@thedrow thedrow modified the milestones: 4.6.0, 5.1.0 Feb 24, 2021
@auvipy auvipy modified the milestones: 5.1.0, 5.3 Sep 20, 2021
@auvipy auvipy modified the milestones: 5.3, 5.4 Jun 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants