Menu

#118 Refactor the tags

Future
wont-fix
nobody
None
1
2019-01-26
2019-01-24
Kpym
No

The current tags do not follow any standard (for example) :

3.0.1
3.1
pgf-3-0-0-rc
start
tag-version-0-97
version-0-98
version-0-99
version-1-00
version-1-01
version-1-09
version-1-10
version-1-18
version-2-00
version-3-0-0

I think that all this tags should be renamed to

v3.0.1
v3.1
v3.0.0rc
v0.1
v0.97
v0.98
v0.99
v1.00
v1.01
v1.09
v1.10
v1.18
v2.00
v3.0.0

to do this you can run :

git tag v3.0.1 3.0.1
git tag -d 3.0.1
git push origin :refs/tags/3.0.1
git tag v3.1 3.1
git tag -d 3.1
git push origin :refs/tags/3.1
git tag v3.0.0rc pgf-3-0-0-rc
git tag -d pgf-3-0-0-rc
git push origin :refs/tags/pgf-3-0-0-rc
git tag v0.1 start
git tag -d start
git push origin :refs/tags/start
git tag v0.97 tag-version-0-97
git tag -d tag-version-0-97
git push origin :refs/tags/tag-version-0-97
git tag v0.98 version-0-98
git tag -d version-0-98
git push origin :refs/tags/version-0-98
git tag v0.99 version-0-99
git tag -d version-0-99
git push origin :refs/tags/version-0-99
git tag v1.00 version-1-00
git tag -d version-1-00
git push origin :refs/tags/version-1-00
git tag v1.01 version-1-01
git tag -d version-1-01
git push origin :refs/tags/version-1-01
git tag v1.09 version-1-09
git tag -d version-1-09
git push origin :refs/tags/version-1-09
git tag v1.10 version-1-10
git tag -d version-1-10
git push origin :refs/tags/version-1-10
git tag v1.18 version-1-18
git tag -d version-1-18
git push origin :refs/tags/version-1-18
git tag v2.00 version-2-00
git tag -d version-2-00
git push origin :refs/tags/version-2-00
git tag v3.0.0 version-3-0-0
git tag -d version-3-0-0
git push origin :refs/tags/version-3-0-0

git push --tags

Then all other collaborators shoud do :

git pull --prune --tags

The only backward compatibility problem could be if some webpage refers to a particular tag in sourceforge (this will break the link).

Discussion

  • Henri Menke

    Henri Menke - 2019-01-24
    • summary: Refactor the tgs --> Refactor the tags
     
  • Henri Menke

    Henri Menke - 2019-01-24

    @cfeuersaenger or @tantau would have to do this. I have insufficient privileges. On the other hand I don't see why this is necessary except for aesthetics.

     
  • Kpym

    Kpym - 2019-01-24

    The tags are here to make simple references to the past versions. If the tags do not follow some convention this do not make the task simpler.
    Another reason is that when you look at the tags at sourceforge they are badly ordered because they do not follow a naming convention.

     
  • Stefan Pinnow

    Stefan Pinnow - 2019-01-25

    You are right, the "old" names of the tags don't follow a convention. But we will follow a convention in the future. We don't like to rename the tags now because the status of all the collaborators currently is unclear and thus we cannot assure that all of them will do the necesary commands.

    When all of them show up again we will discuss this again and decide whether we follow you request or not. Until then, we will (have to) live with it ...

     
    • Kpym

      Kpym - 2019-01-25

      You can also add the new tags vX.X.X and keep the old ones the time to decide to delete them.

       
  • Christian Feuersänger

    Thanks for the request. The naming convention is X.X.X (without the leading 'v').

    The old tags are still useful in order to identify the tags, even if they do still follow CSV naming guides.

     
  • Christian Feuersänger

    • status: open --> wont-fix