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.

Sign up for GitHub

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

Fix a typo in the release hanbook file #694

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Fix a typo in the release hanbook file #694

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
05337b4
fix a typo in the hanbook file
StefanoFioravanzo Jan 25, 2024
f35b999
Fix typo
StefanoFioravanzo Jan 25, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions releases/handbook.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -193,7 +193,7 @@ The manifests repo will be following the release process below:
- [ ] [Assemble a release team](https://github.com/kubeflow/community/issues/571)
- [ ] Create a new [release project](https://github.com/orgs/kubeflow/projects) to track issues and pull requests related to the release
- [ ] Working groups broadly think about features **with priorities** they want to land for that cycle, have internal discussions, perhaps groom a backlog from previous cycle, get issues triaged, etc.
- [ ] Update the release manager and members of the Release Team in the [kubeflow/internal-acls]](https://github.com/kubeflow/internal-acls/pull/545)
- [ ] Update the release manager and members of the Release Team in the [kubeflow/internal-acls](https://github.com/kubeflow/internal-acls/pull/545)
- [ ] Establish a regular release team meeting as appropriate on the schedule and update the [Kubeflow release team calendar](https://calendar.google.com/calendar/embed?src=c_c5i4tlc61oq2kehbhv9h3gveuo%40group.calendar.google.com&ctz=America%2FNew_York)
- [ ] [Propose a release timeline](https://github.com/kubeflow/community/pull/558), announce the schedule to [kubeflow-discuss mailing list](https://groups.google.com/g/kubeflow-discuss), and get lazy consensus on the release schedule from the WG leads
- Review the criteria for the timeline below
Expand Down Expand Up @@ -226,7 +226,7 @@ From that phase and forward updates to the manifests repo must only be fixing co
- Provide a _git revision_ which the release team members or Manifests leads will use to update the files in the manifests repo
- Provide an initial list of issues that the WG would like to close until the final release
- Work on closing the provided open issues
- Ensure that future_git revisions_they provide only include bug fixes, and not new features, from the previously provided _git revision_
- Ensure that future _git revisions_ they provide only include bug fixes, and not new features, from the previously provided _git revision_
- Declare expected common dependency version ranges

**Actions for Manifests WG:**
Expand Down