Suggestion to Cleanup / remove older preview tags #16206
Unanswered
Josverl
asked this question in
Core Development
Replies: 1 comment 1 reply
-
You can implement a policy to delete older vX.Y.Z-preview tags once the corresponding stable version (vX.Y.Z) is released. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In my experience the switch to use the
preview
tags has made is simpler to understand the difference between latest/stable , specific versions and the (latest) preview.But now that we are in the 4th version that uses the preview tag, I wonder if there is any value in keeping the older/non-current preview tags.
or if they can better be removed once the actual corresponding release is made.
From an operational point of view I have already added helper functions to use the "most recent preview" whenever I need "the preview" version,
But I would favor having the tags mirror reality in that there is only a single preview version.
In my understanding each of the 'v-preview` tags point to a commit just before the next version , and I cant see any practical use for them, and sometimes, though not often , they lead to misunderstanding
Could these older tags be removed , and also add that action to the ""release runbook" that I assume exists somewhere
Beta Was this translation helpful? Give feedback.
All reactions