Add template steps for feature freeze - #336
Merged
Merged
Conversation
joestringer
commented
Jul 1, 2025
Member
Author
There was a problem hiding this comment.
I'd be interested in feedback on these changes in terms of:
- The process indicated by these instructions
- How we communicate this process to developers
- Whether this should be handled in the "stable branch" github issue template or a separate template.
joestringer
commented
Jul 1, 2025
| expectations for bandwidth in order to develop, test, review and merge | ||
| the PR. | ||
| ``` | ||
|
|
Member
Author
There was a problem hiding this comment.
I'd also like to integrate severity into this in some way. Perhaps something along the lines of the following labels on PRs:
severity/low: Impact is limited, perhaps only affecting some configurations, or affecting all configurations with acceptable repercussions in a production environment.severity/medium: May force users to take mitigating actions in common scenarios.severity/high: Widespread impact to common deployment configurations.
Member
Author
There was a problem hiding this comment.
Background context further explained in this propsed release blocker workflow: cilium/cilium#32269 (comment)
Member
Author
There was a problem hiding this comment.
I'll defer on this for now, we can always integrate this into the process on top of these changes.
joestringer
force-pushed
the
pr/joe/feature-freeze
branch
from
July 2, 2025 16:57
4a1209c to
30b6eb2
Compare
joestringer
commented
Jul 2, 2025
qmonnet
reviewed
Jul 4, 2025
joestringer
force-pushed
the
pr/joe/feature-freeze
branch
from
July 16, 2025 00:12
30b6eb2 to
59e0029
Compare
Signed-off-by: Joe Stringer <joe@cilium.io>
After a vX.Y.0 minor release, we typically need to do a set of clean up around (a) the upgrade guide on `main`, which now refers to the latest stable release rather than being a placeholder for the upcoming development release, and (b) the oldest stable branch which becomes unmaintained following the new stable release. Document these steps. Signed-off-by: Joe Stringer <joe@cilium.io>
joestringer
force-pushed
the
pr/joe/feature-freeze
branch
from
July 16, 2025 00:13
59e0029 to
6a88d95
Compare
Member
Author
|
Applied all of the proposed fixes. Merging shortly. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Extend the stable and final release processes to account for the communication
that should occur as part of clearly signalling to the development community
the state of the development cycle and any actions that contributors need to
take with respect to stable branches.
Also fixes: #302