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.

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

Security WG roadmap for KF 1.9 #2598

Closed
8 of 10 tasks
rimolive opened this issue Jan 22, 2024 · 5 comments
Closed
8 of 10 tasks

Security WG roadmap for KF 1.9 #2598

rimolive opened this issue Jan 22, 2024 · 5 comments

Comments

@rimolive rimolive converted this from a draft issue Jan 22, 2024
@rimolive rimolive changed the title Security WG roadmap Security WG roadmap for KF 1.9 Jan 22, 2024
@rimolive rimolive moved this from Todo to In Progress in 1.9 Release Jan 24, 2024
@StefanoFioravanzo
Copy link
Member

StefanoFioravanzo commented Feb 28, 2024

Hello @akgraner @juliusvonkohout, this is a kind reminder that Monday, March 4th will be our Kubeflow 1.9 release development checkpoint, we will be halfway through our dev cycle, and we expect most of the work to be well underway (reminder: code freeze is scheduled for Apr 15th)

Can you please acknowledge your status with respect to your roadmap, comment on the progress made so far, and provide an assessment of the work that remains?

Does the comment above reflect the work that will be delivered as part of Kubeflow 1.9? Is it up to date?

@juliusvonkohout
Copy link
Member

@StefanoFioravanzo i updated the top post with information.

@StefanoFioravanzo
Copy link
Member

@juliusvonkohout Why do you say a merged PR (first one) is in progress? Merged PR should mean "checked" box I guess. If that's not valid, what else needs to be done?

@juliusvonkohout
Copy link
Member

I checked the boxes for you :-D

@rimolive
Copy link
Member Author

This is done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: Done
Development

No branches or pull requests

3 participants