-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[TRACKING] Kubeflow 1.10.0 (Notebooks WG Components) #7459
Comments
@kimwnasptd please suggest/add things you want to include in 1.9.0 to this tracking issue. |
Hello @kubeflow/wg-notebooks-leads, 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? Understandably, the design phase for Notebooks 2.0 seems to still be in progress. Is it still applicable to consider Notebooks 2.0 part of the KF 1.9 release, even in alpha phase? Also, can you please update the above comment with the list of 1.8.1 issues that could not be fixed in that patch release, and list them out here? There are still unfinished sections above. Let's try and have a short but clear comment with all the work that is still pending for a successful release. Please proactively let the release team know if there are delays, blockers, or uncertain situations, know so that we can align expectations and try and help you out, if possible. |
Hello @kubeflow/wg-notebooks-leads! As you might have seen from kubeflow-discuss, we cut Kubeflow 1.9 RC0. We are already behind schedule with the release timeline, and we wanted to allow the distribution owners to start testing the new features. We (the @kubeflow/release-team) are aware that this release candidate does not contain any Notebooks enhancements. We can work with the release team to help you out, if you give us very specific instructions. What PRs need merging and what work remains? Please consider that folks may not be familiar with this codebase or with the issues at hand, but we are willing to try and help if you give us enough context and direction What can we do to help you cut a Notebooks release by next Monday, May 13th? We will then include that release in Kubeflow 1.9 RC1. |
@juliusvonkohout I see that these are old PRs. Are they mergeable? If not, we need a committed plan for both and someone to take ownership for either re-implementation, or review, or merging. |
I think so, but @thesuperzapper and @kimwnasptd can answer that. |
For those watching, this issue was actually tracking the "next" release (which at the time of creation was Please raise any showstopping issues or critical PRs we need to get merged on that issue instead. |
This issue is to track what we are planning to include in Kubeflow 1.10.0, specifically the components owned by the Notebook WG, we will likely have moved at least some of the components to their own repos for the 1.10.0 release (#7549).
Old Tracking Issues
Changes for
1.10.0
Headline Features
Tensorboards
The text was updated successfully, but these errors were encountered: