release: Add 1.6 release team

[kimwnasptd]

Following the release of KF 1.5, let's use this issue to track the formation of the KF 1.6 release team.

After the discussion in the 1.5 release retro and the progression of the last two releases we've decided to put more focus on distributing the release effort across the release team members. For this we will be focusing more on the WG liaison roles, so each team member will be assigned to a WG.

Release team members will be responsible for joining the meetings of their assigned WGs and help with the communications with WGs across the release. Note that more than 1 member can be assigned to the same WG.

And with this, we'd like to welcome everyone to participate in the 1.6 release team! We are looking forward to new members joining the team and interacting with the WGs.

For the 3 lead roles we have currently converged on @annajung being the Release Manager of the KF 1.6 release team in:

• The last two release team meetings [1] [2]
• In the Community Meeting at 12/4/2022 (will add a link once it's out)

But if you'd be interested for one of the lead roles feel free to speak up as well! This way the current leads can evaluate more people and also assign shadows for these roles to cultivate the next leads.

You can take a look at the handbook in: https://github.com/kubeflow/community/blob/master/releases/handbook.md

cc @kubeflow/release-team @kubeflow/wg-pipeline-leads @kubeflow/wg-manifests-leads @kubeflow/wg-notebooks-leads @kubeflow/wg-training-leads @kubeflow/wg-automl-leads @pvaneck @yuzisun @zijianjoy @jbottum

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kimwnasptd

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:

• releases/OWNERS [kimwnasptd]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kimwnasptd]

/hold until April 25th, 2022 11:59 pm US Pacific Time

This is the date we will also merge the timeline #558

I'll be extending the PR with commits to include more people as we get more comments

[mstopa]

Hey @kimwnasptd, hey Team, I will be happy to join

[kimwnasptd]

@mstopa that's awesome! Do you have a preferred WG which you'd like to help with communications throughout the release?

[kimwnasptd]

Regarding the distributions, let's also try to gather the representatives early on for this one. This is the previous list we had kubeflow/manifests#2146 (comment)

Distribution	Representatives
Arrikto EKF	@kimwnasptd
Arrikto MiniKF	@kimwnasptd
Azure	❓
AWS	@surajkota @akartsky
Charmed Kubeflow	@DomFleischmann
Google Cloud	@zijianjoy
IBM	@yhwang
Nutanix	@johnugeorge
Kubeflow with Argo CD	@davidspek
Openshift	@nakfour @LaVLaS

From anyone referenced above, will this be the case for the KF 1.6 release as well?

Also, as a side note, I think we should remove Azure in 1.6 since it hasn't been maintained for more than 2 versions

[yhwang]

From anyone referenced above, will this be the case for the KF 1.6 release as well?

Yes for me.

[jbottum]

I am willing to help with the product management responsibilities as the lead PM or as a shadow.

[DomFleischmann]

I would like to join again as a Release Team member, my preferred WGs to help with communications would be Manifests or Pipelines.

[DnPlas]

I'd like to be part of the team as a Release Team Member. My preferred WG is training.

[mstopa]

@mstopa that's awesome! Do you have a preferred WG which you'd like to help with communications throughout the release?

@kimwnasptd I've got no preferred WG yet, I could assist you with Notebooks, or help in communications with Serving or focus on another group of your choice

[LaVLaS]

@kimwnasptd Can you update the OpenShift representatives to be @VaishnaviHire and @LaVLaS? We are working on getting all of the KF on OpenShift info updated to latest in preparation for testing KF 1.6 early

[annajung]

Hi @kimwnasptd, we finalized the release team and their role during the release team meeting on April 25th except Docs lead

WG Liaisons are

• Pipelines: Dominik
• KServe: Maciek
• Manifests: Dominik, Kimonas, Daniela
• Notebooks: Kimonas, Maciek
• Training Operators: Daniela
• Katib: Anna

Product Manager(s): Josh, Amber, and Dominik

[annajung]

@kimwnasptd Another update, Vedant confirmed his role as Docs lead.

For docs, Vedant will lead with Amber shadowing and myself assisting when needed.

We should all be set for the release team! :)

[surajkota]

Hey folks, I am interested to help from KServe side as well in addition to AWS Distribution representative. I am on vacation till 05/28 but will be joining starting June.

[annajung]

Hi @kimwnasptd, here is another update of the finalized list of release team members

WG Liaisons are

• Pipelines: Dominik, Kartik
• KServe: Maciek, Suraj
• Manifests: Dominik, Kimonas, Daniela
• Notebooks: Kimonas, Maciek
• Training Operators: Daniela
• Katib: Anna

Product Manager(s): Josh, Amber, and Dominik
Docs Lead(s): Vedant, Amber, and Anna

[gauravpawar13]

@annajung I'd like to become a part of release team member

[kimwnasptd]

@annajung @kubeflow/release-team I've updated the commits with all comments above. Feel free to take another look.

If you are OK I think we can move forward with merging this PR as well

[annajung]

Thanks Kimonas!
/lgtm

@gauravpawar13, you are welcome to participate and join the release team meeting

[annajung]

/hold cancel