Add 1.7 release timeline #573
Conversation
Commit with initial timeline proposal.
releases/release-1.7/README.md
Outdated
| - **Wednesday, Sep 28th 2022**: Week 1 - Release Team is formed | ||
| - **Wednesday, Sep 28th 2022**: Week 1 - Release Cycle Begins | ||
| - **Wednesday, Oct 12th 2022**: Week 3 - Roadmaps are finalized | ||
| - **Wednesday, Jan 18th 2023**: Week 17 - Feature Freeze |
There was a problem hiding this comment.
not a blocker, note that Jan 16th is U.S. Holiday
releases/release-1.7/README.md
Outdated
| - **Wednesday, Feb 1st 2023**: Week 19 - Distribution Testing Starts | ||
| - **Wednesday, Feb 22nd 2023**: Week 22 - Distribution Testing Ends | ||
| - **Tuesday, Feb 28th 2023**: Week 23 - Docs Update Ends |
There was a problem hiding this comment.
tagging previous distribution owners to give feedback
@julioo @VaishnaviHire @LaVLaS @johnugeorge @yhwang @zijianjoy @gkcalat @surajkota @kimwnasptd
There was a problem hiding this comment.
LGTM
One question: it seems that we are planning to update docs before releasing Kubeflow. Could they happen on the same day?
There was a problem hiding this comment.
@gkcalat there might be a confusion between Docs Updates and Docs Publishing. We expect all the docs changes that working groups or distribution owners have to be ready the day before so that we don't have to wait for any late changes on the day of the release and just publish the documentation. Does that make sense?
There was a problem hiding this comment.
@DomFleischmann thank you. Sounds good. The issue I mentioned is that the website is watching the master branch. As long as we merge new docs in the repo, the updated docs go live.
|
Sounds good for the Kubeflow 1.7 timeline. |
|
@DomFleischmann Per conversation, we might consider a milestone in week 4 or 5 that requests the Working Groups to identify their members. It might be good to identify Working Group members who are helping on the WG docs, test plan and/or test infra for example. |
Move Feature Freeze data by 1 week due to holidays.
|
LGTM |
|
/lgtm |
After the last communtiy meeting we agreed to push the Roadmap finalization date to October 19th to give WGs more time and for the roadmaps being presented during Kubeflow Summit.
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: annajung, DomFleischmann The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Is Kubeflow 1.7 still being released today (March 8, 2023) or has this timeline slipped? |
|
@techjournalist thanks for your question. @DomFleischmann is the 1.7 release manager and sets the schedule. As communicated in our last Release Team and Community meetings, the current date is March 15. That said, the AWS team has recently opened an issue to fix some items in the 1.7 release candidate. It looks like we have a path to fix those items, cut a new release candidate and complete another round of distribution testing. It will be Dominik's call on the schedule and the features, which we review on Monday in the Release Team call and again on Tuesday in the Community call. |
|
Do we have any tentative timeline for Kubeflow v1.7 being released for OpenShift ? |
Based on the 1.6 release date, September 7th, this is a proposed timeline for the 1.7 release.
This timeline will be discussed further in today's (19th of September) release team meeting.
Please review and provide feedback by September 28th, 2022.
cc @kubeflow/release-team @kimwnasptd @kubeflow/wg-pipeline-leads @kubeflow/wg-manifests-leads @kubeflow/wg-notebooks-leads @kubeflow/wg-training-leads @kubeflow/wg-automl-leads @yuzisun @zijianjoy @jbottum @annajung @johnugeorge