Update template for minor releases - #424
Conversation
| - [ ] The oldest maintained release branch will now no longer be maintained. | ||
| Prepare an update PR for the `main` branch to remove references to that | ||
| branch. This may involve modifying documentation, code comments and | ||
| configuration for GitHub or Renovate. | ||
| - `git grep vX.Y-2` |
There was a problem hiding this comment.
We still need this right? main still refers to v1.17 right now all over the place. Renovate etc
There was a problem hiding this comment.
Background timing to this is:
Branching usually happens around the start of the month. Means that the final release for the oldest branch happens 2 weeks after branching. We can't disable the main branch references to oldest stable as part of stable branch creation.
We then do the stable release in the middle of the month. That includes the final release for the to-be-EOL stable branch.
Then typically we do the new minor around the end/start of the month. At that point we can for sure remove all the references to the old branch.
There was a problem hiding this comment.
We still need to keep this and I need to check for v1.17 in main branch. (I think Julian did for renovate)
Signed-off-by: André Martins <andre@cilium.io>
2271759 to
8cc11e7
Compare
2 participants
No description provided.