-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Improvement tasks for v1.6 release cycle #9104
Comments
/cc @kubernetes-sigs/cluster-api-release-team |
/triage accepted |
@killianmuldoon @sbueringer @joekr while the all improvements tasks polished up now, i have only one sub task without a clear understanding what needs to be done:
Do you have any idea what exactly needs to be done to accomplish ^ task? |
I can only guess, but I think doc.crds.dev only adds a new version to the list if someone calls it once. Probably after that it's also used as "latest". I think the links in our docs/book point to "latest", e.g. https://doc.crds.dev/github.com/kubernetes-sigs/cluster-api |
Yeah - if I remember right this link: https://doc.crds.dev/github.com/kubernetes-sigs/cluster-api@latest needs to be called at least once before it's cached as the base page for the repo. The idea of that task was to automate that update - but it might be a good idea to initially add checking that page as a task during the release process. Automation can come after documented the manual process initially. |
To be honest. I'm not sure if it's worth automating clicking a link if we do it once every 4 months. Maintaining automation also comes with a cost |
I do not know why, but when I click the above link, I have list of CRDs from v1.4.5, should we change it to point to latest? |
@killianmuldoon is it after the release is cut when we have to check it? Also, talking to @joekr offline, got to know about this automation: https://github.com/oracle/cluster-api-provider-oci/blob/main/.github/workflows/release.yaml#L28-L31 Perhaps, we could also make use of it same way? |
I get the same, I have no idea |
Sounds okay as a very last step. I don't want to manually re-run stuff if this curl somehow fails |
@furkatgofurov7 can you assign me to Consider implementing a tool to generate our ProwJob YAMLs to make the jobs easier to manage I'll open an issue to track it |
Sure, assigned to you @killianmuldoon |
@killianmuldoon did you have time to open a separate issue for this, if so, can you please point me to it? |
@furkatgofurov7 I've created and issue here: #9257 |
@furkatgofurov7 can you add a task for ensuring the new 🚀 emoji passes the source code courtesy of Cecile (slack comment and src link) |
Related issue: kubernetes-sigs/kubebuilder-release-tools#54 |
👋 @furkatgofurov7 I can take this one:
would be helpful if someone from comms team can provide a bit of context for why we are making this change as well |
Thanks @cahillsf, updated the issue with your name. @g-gaston was the idea here to build the tool once from main branch and use that for release branches without needing to regenerate it separately? @cahillsf in any case, let's open a separate issue to track it and we can discuss the details over there |
👋 @furkatgofurov7 I can take this one too:
Although I need to understand this a bit better myself. I will miss the beta release cut tomorrow unfortunately but can watch the recording to catch up. |
👋 hey @furkatgofurov7 all feel free to close out this issue |
@cahillsf how about:
they seem to be not in the GH board, which is obvious because you need either a separate issue or PR to add it to the board. Are you planning to create a separate issue in the repo and then add them to the board? |
Ah right good catch - I only moved over the tasks with existing issues, will cut issues for the remainder to add to the new project board |
hey @furkatgofurov7 should be good here. the only one that i did not open as issue for is:
will bring up for discussion in our kickoff RT meeting to see if we want to formalize this as an issue |
There is an existing issue for that already, so you can just track it: #9319 |
@furkatgofurov7: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
NOTE: Issue is created based on #8418 to avoid ownership issues when there is a need for editing issue descriptions, assigning it to folks, etc. To check conversations in the previous cycle improvement tasks tracking issue, refer to #8418 (v1.5 release cycle) and #7524 (v1.4 release cycle).
NOTE2: The list of team-specific sub-tasks below are prioritized from highest priority sub-tasks to lowest from top to down accordingly, and priorities were agreed upon after triaging this issue collectively with the RT folks and repo maintainers. To see the notes from the triaging, please see: https://hackmd.io/@BcPM2Mr1SieWG3EZ0p5rGg/capi-improvement-tasks-v1-6
NOTE3: Each sub-task description has a GH handle next to it, meaning a sub-task is assigned to that person and he/she is actively working on it. If you would like to work on any unassigned sub-task feel free to comment on this umbrella issue 🙂
CI Signal/Bug Triage/Automation Manager Team sub-tasks
won't do/cancelled
] Having a team alias in the OWNER/OWNER_ALIASES file so that it could be potentially used as a single source of truth where we need to know the list of release team members - could be used in some kind of automation. (@furkatgofurov7)@cluster-api-release-team
when auto-opening the PR to promote images from staging to prod #7487 (comment)won't do/cancelled
since anyways there is no point of cc ng RT members who themselves will be creating image promotion PR on the release cutting call.won't do/cancelled
] cc release team on cherry-pick PRs (@cahillsf)won't do/cancelled
] Improve the Homebrew publish processCommunications/Docs/Release Notes Manager Team sub-tasks
Misc sub-tasks
won't do/cancelled
] Explore the idea of "an issue triage team" - a team that is responsible for triaging issues that come into the repo. (@furkatgofurov7)The text was updated successfully, but these errors were encountered: