Update Release Team for 1.7

[DomFleischmann]

After the Release Team being officially formed (see #kubeflow/community/issues/571). We need to update the acls with the new members and new roles.

Tagging all members in case I missed something:
@anencore94 @annajung @bradleykcardwell @chalesa101 @DnPlas @jbottum @kimwnasptd @shivaylamba @surajkota @Rishit-dagli @yubozhao

[DomFleischmann]

@chensun @james-jwu

This PR has been open for quite some time, it is failing due to these PRs not being merged yet:
#579 #578

Can we address this? We will need some of these permissions to cut the 1.7 release.

[chensun]

@chensun @james-jwu

This PR has been open for quite some time, it is failing due to these PRs not being merged yet: #579 #578

Can we address this? We will need some of these permissions to cut the 1.7 release.

I see neither PR follows the guideline documented here: https://github.com/kubeflow/internal-acls#joining-kubeflow-github-organization
Did they ever contributed to Kubeflow before? If not, what qualifies them to join the release team, and who sponsors them?

[DomFleischmann]

@chensun @james-jwu
This PR has been open for quite some time, it is failing due to these PRs not being merged yet: #579 #578
Can we address this? We will need some of these permissions to cut the 1.7 release.

I see neither PR follows the guideline documented here: https://github.com/kubeflow/internal-acls#joining-kubeflow-github-organization Did they ever contributed to Kubeflow before? If not, what qualifies them to join the release team, and who sponsors them?

Thanks for clarifying @chensun I can vouch for @yubozhao (#579). He is part of the BentoML team who are contributing an integration with Kubeflow and their product (see this pr). He has also been very active in the Release Team joining all the meetings.

[DomFleischmann]

@chensun I have removed the members who are still not in the org as we need to start cutting the release in 2 days. Can this be reviewed now?

[chensun]

/lgtm

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chensun, 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:

• OWNERS [chensun]

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

[DomFleischmann]

Hey, @chensun it seems like I still don't have permission. Are there any further steps required?

[chensun]

Hey, @chensun it seems like I still don't have permission. Are there any further steps required?

Sync is broken, I'll try investigating the issue today.

[DomFleischmann]

Thank you @chensun for looking into this!

[DomFleischmann]

@chensun Could you create a v1.7-branch branch in the kubeflow/kubeflow repository? Not being able to creat this branch is currently blocking us.

[chensun]

@DomFleischmann Created https://github.com/kubeflow/kubeflow/tree/v1.7-branch

I looked into the sync issue yesterday, but haven't found a solution yet. I'll post details in the issue and keep digging into it.

[jbottum]

@theadactyl @james-jwu @chensun is there an update on this issue. We are trying to move the 1.7 RC forward and I understand this is a blocking issue.

[chensun]

@jbottum I created the branch requested, and I think release team should have been temporarily unblocked? Let me know if there's any other action you may need help due to permission issues.
Meanwhile, I'm still looking into the broken sync issue, I'll update progress on #587.

[jbottum]

@chensun thank you @DomFleischmann are you unblocked ?