Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fix release crawler for LWKD #11182

Closed
fabriziopandini opened this issue Sep 15, 2024 · 8 comments
Closed

Fix release crawler for LWKD #11182

fabriziopandini opened this issue Sep 15, 2024 · 8 comments
Assignees
@Sunnatillo
Labels
area/release Issues or PRs related to releasing good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@fabriziopandini
Copy link
Member

fabriziopandini commented Sep 15, 2024 •
edited
Loading

What would you like to be added (User Story)?

As a users I would like to be informed about new CAPI releases
As a maintainer/release team I would like to be spread the voice about new CAPI releases

Detailed Description

LWKD is weekly email with news about the K8s ecosystem
It seems that the configuration of the crawler that looks up for changes in subproject is wrong WRT to Cluster API, we should fix it!

Anything else you would like to add?

Based on my understanding this is where the fix should be done

  • here - Wrong url
  • here - Cluster API should move from kubernetes to kubernetes-sigs

Label(s) to be applied

/kind feature
/area release

cc @kubernetes-sigs/cluster-api-release-team
@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. area/release Issues or PRs related to releasing needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Sep 15, 2024
@fabriziopandini fabriziopandini added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Sep 15, 2024
@kubernetes-sigs kubernetes-sigs deleted a comment from k8s-ci-robot Sep 16, 2024
@Sunnatillo
Copy link
Contributor

/assign

@chrischdi
Copy link
Member

Thanks @Sunnatillo for opening the PR!

xref:

@Sunnatillo
Copy link
Contributor

/close

@k8s-ci-robot
Copy link
Contributor

@Sunnatillo: Closing this issue.

In response to this:

/close

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-sigs/prow repository.

@chrischdi
Copy link
Member

/reopen

I created:

To fix some more :-)

@k8s-ci-robot
Copy link
Contributor

@chrischdi: Reopened this issue.

In response to this:

/reopen

I created:

To fix some more :-)

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-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot reopened this Oct 9, 2024
@chrischdi
Copy link
Member

Also merged.

If we are right we should see the patch releases in the next newsletter 🎉

/close

@k8s-ci-robot
Copy link
Contributor

@chrischdi: Closing this issue.

In response to this:

Also merged.

If we are right we should see the patch releases in the next newsletter 🎉

/close

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-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Sunnatillo Sunnatillo

Labels
area/release Issues or PRs related to releasing good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
CAPI v1.9 release improvement tasks
Status: Done
Milestone
No milestone
Development

No branches or pull requests
4 participants
@chrischdi @fabriziopandini @k8s-ci-robot @Sunnatillo