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
Prepare for v1.15 development cycle #26516
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reviewed for my files.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
contributing changes LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Datapath looks good, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Discussed with Joe offline:
- Since we are close to merging ci: use Ariane to trigger workflows #26237, we will merge it first before branching off as it will simplify the process considerably.
- In particular, for this PR it means we do not need to make copies of the workflows for 1.14. Instead, workflows for 1.14 will live directly on the 1.14 branch. This is handled as part of v1.14: ci: use Ariane to trigger workflows #26625.
a8c044c
to
127d2b3
Compare
@@ -19,6 +19,6 @@ jobs: | |||
- uses: docker://quay.io/cilium/scruffy:v0.0.3@sha256:ca997451b739cbf03c204cb2523a671c31c61edc606aa5d20dc3560bc7f25bc7 | |||
with: | |||
entrypoint: scruffy | |||
args: --git-repository=./ --stable-branches=origin/main,origin/v1.9,origin/v1.10,origin/v1.11,origin/v1.12,origin/v1.13 | |||
args: --git-repository=./ --stable-branches=origin/main,origin/v1.9,origin/v1.10,origin/v1.11,origin/v1.12,origin/v1.13,origin/v1.14 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Nit] Should we remove v1.9 and v1.10 from here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah we probably should. I have another PR in the works to drop all 1.11 or earlier references, which should wait until the release. I can add this change into that one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -14,26 +14,31 @@ on: | |||
- Cilium L4LB XDP (ci-l4lb-1.11) | |||
- Cilium L4LB XDP (ci-l4lb-1.12) | |||
- Cilium L4LB XDP (ci-l4lb-1.13) | |||
- Cilium L4LB XDP (ci-l4lb-1.14) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Useless nit] The ci-xxx-1.xx
workflows do not exist anymore, now it's only the regular non -1.xx
versions for all branches. Not that it matters considering Loki is disabled anyway...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I was debating if we should just be deleting the loki workflow instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😇
Signed-off-by: Joe Stringer <joe@cilium.io>
127d2b3
to
72064d9
Compare
Depends on: #26237 (which introduces per-branch comment-trigger workflows, so this PR doesn't need them)
This should be merged once we prepare the v1.14 branch.
Differences from the previous dev cycle preparation PR:
v1.15-dev
version during the dev cycle.