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

Add 1.4 release information #1974

Merged
merged 3 commits into from
Aug 25, 2021
Merged

Add 1.4 release information #1974

merged 3 commits into from
Aug 25, 2021

Conversation

annajung
Copy link
Member

Signed-off-by: Anna Jung (VMware) [email protected]

Description of your changes:
Based on discussion of improving file structure for the release,

  • rename directory release to releases
  • add release-1.4 directory
  • add release-1.4/README.md with release timeline and relevant links
  • add release-1.4/release-team.md with name of all release members

Checklist:

  • Unit tests pass:
    Make sure you have installed kustomize == 3.2.1
    1. make generate-changed-only
    2. make test

cc @RFMVasconcelos @davidspek @mkbhanda @kimwnasptd

Comment on lines 7 to 10
| Product Manager | |
| Docs Lead | Rui Vasconcelos (GitHub: [@RFMVasconcelos](https://github.com/RFMVasconcelos) / Slack: `@Rui Vasconcelos`) |
| Working Group Liaison(s) | |
| Distribution Representative | |
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have anyone serving as a product manager? WG liaison? distribution rep?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These roles are defined in the release hanbook

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hi @jbottum, during the release team meeting today, your name was brought up as the product manager for the 1.4 release. Could you confirm your commitment to the role? Once confirmed, I'll update the markdown to add your info.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Regarding the WG liaisons I'd propose the following people for this release, who have helped with the release issues:

WG handle
AutoML @andreyvelich
Manifests @kimwnasptd
Notebooks @kimwnasptd
Pipelines @Bobgy @zijianjoy
Serving @pvaneck
Training @johnugeorge @Jeffwan @terrytangyuan

@annajung @mkbhanda we could also add a bullet for defining the WG liaisons in the preparation phase. WDYT?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@annajung yes, I will act as the product manager for the 1.4 release.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

member list updated with the proposed WG liaisons and product manager, PTAL

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we could also add a bullet for defining the WG liaisons in the preparation phase. WDYT?

@kimwnasptd Do you mean add a step to find out who will be acting as a liaison for each WG during preparation phase?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kimwnasptd Do you mean add a step to find out who will be acting as a liaison for each WG during preparation phase?

Correct. Essentially the release team will need to know who these people are early on so they can start pinging them in issues, i.e. 2 weeks before the feature freeze to provide them branches/versions etc.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@rui-vas
Copy link

rui-vas commented Aug 16, 2021

Thank you for leading this @annajung!

I know that @knkski - Kenneth Koski - wanted to join as a shadow. Can you please confirm @knkski?

If that's the case, @annajung could you please add @knkski to this PR?

@knkski
Copy link

knkski commented Aug 23, 2021

Yes, I would be interested in shadowing for this release 👍

Signed-off-by: Anna Jung (VMware) <[email protected]>
@Bobgy
Copy link
Contributor

Bobgy commented Aug 24, 2021

/lgtm
thanks for the early update!
Feel free to ping me when the PR is ready.

EDIT: ohh this is manifests repo, then the release manager should approve this instead.

@kimwnasptd
Copy link
Member

Thank you for pushing this @annajung! Let's merge this first iteration to have the schedule and team committed to GH.
I'll follow up with an issue to get the distribution reps for this release, so that we can add them in a subsequent PR.

/lgtm
/approve

@google-oss-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

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

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

@google-oss-robot google-oss-robot merged commit fe99bd7 into kubeflow:master Aug 25, 2021
kimwnasptd added a commit to arrikto/kubeflow-manifests that referenced this pull request Aug 31, 2021
* Add 1.4 release information

Signed-off-by: Anna Jung (VMware) <[email protected]>

* Add 1.4 release wg liaisons, product manager and a shadow

Signed-off-by: Anna Jung (VMware) <[email protected]>

* Add a step to reach out to each WG during preparation for WG liaison info

Signed-off-by: Anna Jung (VMware) <[email protected]>
google-oss-robot pushed a commit that referenced this pull request Aug 31, 2021
* Add 1.4 release information (#1974)

* Add 1.4 release information

Signed-off-by: Anna Jung (VMware) <[email protected]>

* Add 1.4 release wg liaisons, product manager and a shadow

Signed-off-by: Anna Jung (VMware) <[email protected]>

* Add a step to reach out to each WG during preparation for WG liaison info

Signed-off-by: Anna Jung (VMware) <[email protected]>

* docs: fix fmt (#1992)

* Allocate 3 weeks for distribution testing (#1996)

Signed-off-by: Kimonas Sotirchos <[email protected]>

* Update pipelines to 1.7.0 (#1997)

Signed-off-by: Kimonas Sotirchos <[email protected]>

* Update README for pipelines 1.7.0

Signed-off-by: Kimonas Sotirchos <[email protected]>
Tomcli pushed a commit to IBM/manifests that referenced this pull request Sep 22, 2021
* Cherry pick updates to the RC 0 (kubeflow#2000)

* Add 1.4 release information (kubeflow#1974)

* Add 1.4 release information

Signed-off-by: Anna Jung (VMware) <[email protected]>

* Add 1.4 release wg liaisons, product manager and a shadow

Signed-off-by: Anna Jung (VMware) <[email protected]>

* Add a step to reach out to each WG during preparation for WG liaison info

Signed-off-by: Anna Jung (VMware) <[email protected]>

* docs: fix fmt (kubeflow#1992)

* Allocate 3 weeks for distribution testing (kubeflow#1996)

Signed-off-by: Kimonas Sotirchos <[email protected]>

* Update pipelines to 1.7.0 (kubeflow#1997)

Signed-off-by: Kimonas Sotirchos <[email protected]>

* Update README for pipelines 1.7.0

Signed-off-by: Kimonas Sotirchos <[email protected]>

* Cherry-pick: Use MPI operator tag v0.3.0 (kubeflow#2019)

Ensure the v1 controller is used.

* Cherry pick of kubeflow#2024: Update training operator to v1.3.0-rc.1 (kubeflow#2026)

* Cherry-picks: Manifest updates for 1.4 kubeflow#2006 kubeflow#2013 kubeflow#2008 kubeflow#2021#2020 (kubeflow#2022)

* Update KFP Tekton for version 1.0.0 (kubeflow#2006)

* Update KFP Tekfont for version 1.0.0

Used tag https://github.com/kubeflow/kfp-tekton/tree/v1.0.0/manifests/kustomize

Signed-off-by: Kimonas Sotirchos <[email protected]>

* Update the README

Signed-off-by: Kimonas Sotirchos <[email protected]>

* feat: add seldon permissions to default-editor (kubeflow#2013)

* Create kubeflow-edit-seldon.yaml

* Update kustomization.yaml

* Update manifests for Katib 0.12.0-rc.1 release (kubeflow#2008)

* Update manifests for Katib 0.12.0-rc.1 release

* Update README

* Update Notebooks WG manifests from RC1 (kubeflow#2021)

Use the manifests from https://github.com/kubeflow/kubeflow/tree/v1.4-rc.1

Signed-off-by: Kimonas Sotirchos <[email protected]>

* git: Ignore Vim files (kubeflow#2020)

Signed-off-by: Kimonas Sotirchos <[email protected]>

* Add IKS files

- Add orignal distributions folder as dist and remove
  non-IKS files, except OpenShift
- Add `iks-single` for single user deployment
- Add `iks-multi` for multiple user deployment

Signed-off-by: Yihong Wang <[email protected]>

* remove openshift related files

Signed-off-by: Yihong Wang <[email protected]>

* Add Application CRD

Add Application CRD and an application object
to specify kubeflow version and show on centraldashboard.

Signed-off-by: Yihong Wang <[email protected]>

Co-authored-by: Kimonas Sotirchos <[email protected]>
Co-authored-by: Aldo Culquicondor <[email protected]>
Co-authored-by: Jiaxin Shan <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants