From bab59eb97b607b93c88b8e108ef9a5e8d55b667c Mon Sep 17 00:00:00 2001 From: Kimonas Sotirchos Date: Mon, 22 Nov 2021 17:22:50 +0200 Subject: [PATCH 1/5] handbook: Add concrete step for tracking issue We had discussed that it would help visibility if there's a single tracking issue for the release, and not only tracking issues for each WG. Signed-off-by: Kimonas Sotirchos --- releases/handbook.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/releases/handbook.md b/releases/handbook.md index 5358d298a..f1b6312bb 100644 --- a/releases/handbook.md +++ b/releases/handbook.md @@ -194,7 +194,11 @@ Criteria for timeline that the team needs to consider - Kubecon dates - let’s not hard block on events, but keep them in mind since we know community members might get doublebooked. - Associated events (aka. AI Day at Kubecon, Tensorflow events) - we want to keep them in mind. -**Success Criteria:** Release team selected, schedule sent to kubeflow-discuss, all release team members have the proper permissions and are meeting regularly. +**Success Criteria:** +* Release team selected +* Schedule sent to kubeflow-discuss +* All release team members have the proper permissions and are meeting regularly +* A tracking issue for the release has been created in kubeflow/community ### Development (10 weeks) From 8de526ef1f3966dab712caeea10882f9c868e0a7 Mon Sep 17 00:00:00 2001 From: Kimonas Sotirchos Date: Mon, 22 Nov 2021 17:29:31 +0200 Subject: [PATCH 2/5] handbook: Add more details to the timeline table Expose information like the RCs that will be cut between the different phases. Signed-off-by: Kimonas Sotirchos --- releases/handbook.md | 39 +++++++++++++++++++-------------------- 1 file changed, 19 insertions(+), 20 deletions(-) diff --git a/releases/handbook.md b/releases/handbook.md index f1b6312bb..c2ed5c33e 100644 --- a/releases/handbook.md +++ b/releases/handbook.md @@ -155,26 +155,25 @@ The manifests repo will be following the release process below: ## Timeline - -| Week | Events | -| --- | --- | -| 1 | Development | -| 2 | | -| 3 | | -| 4 | | -| 5 | | -| 6 | | -| 7 | | -| 8 | | -| 9 | | -| 10 | | -| 11 | Feature Freeze, Documentation | -| 12 | | -| 13 | Manifests testing week | -| 14 | Distributions testing | -| 15 | | -| 16 | | -| 17 | Release | +| **Week** | **Who** | **What** | +| -------- | ------- | -------- | +| Week 0 | Release Manager | [Preparation](#preparation) | +| Week 1 | Release Manager | Start of Release Cycle | +| Week 1 | Community | [Development](#development-10-weeks) | +| Week 10 | Release Team | [Feature Freeze](#feature-freeze-2-weeks) | +| Week 10 | Manifest WG | [rc.0 Released](#feature-freeze-2-weeks) | +| Week 10 | Docs Lead | [Documentation](#documentation) | +| Week 10 | Manifest WG | [rc.1 Released](#feature-freeze-2-weeks) | +| Week 12 | Release Team | [Manifests Testing](#manifests-testing-1-week) | +| Week 13 | Docs Lead | End of [Documentation](#documentation) | +| Week 13 | Release Team | End of [Manifests Testing](#manifests-testing-1-week) | +| Week 13 | Manifest WG | [rc.2 Released](#manifests-testing-1-week) | +| Week 14 | Release Team and Distribution Representative | [Distribution Testing](#distribution-testing-3-weeks) | +| Week 17 | Release Team and Distribution Representative | End of [Distribution Testing](#distribution-testing-3-weeks) | +| Week 17 | Manifest WG | (optional) [rc.3 Released](#distribution-testing-3-weeks) | +| Week 17 | Release Team | [Release Day](#release) | +| Week 17 | Release Team | Publish Release Blog | +| TBD | Community | Release Retrospective | ### Preparation From de5446661a23cdf1e85b0c2731ae921c506036d6 Mon Sep 17 00:00:00 2001 From: Kimonas Sotirchos Date: Mon, 22 Nov 2021 17:59:27 +0200 Subject: [PATCH 3/5] handbook: Features PR should have docs PRs Encourage WGs to enforce contirbutors to also have docs PRs in parallel with feature PRs. This will help the docs effort since we will have a better understanding of what PRs still need to be merged for a release. Signed-off-by: Kimonas Sotirchos --- releases/handbook.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/releases/handbook.md b/releases/handbook.md index c2ed5c33e..c0c7c4dce 100644 --- a/releases/handbook.md +++ b/releases/handbook.md @@ -205,7 +205,10 @@ Criteria for timeline that the team needs to consider Normal development in the different WGs and in the repo. **Success Criteria:** -* (Optional but encouraged): Issues tracking new features should also provide information on whether the docs should be updated for that feature +* (Optional but encouraged): Issues tracking new features should also have a + corresponding docs PR that gets developed in parallel with the feature. + This will help keep track of PRs at risk during the Feature Freeze phase as + well as evaluate the docs effort early. ### Feature Freeze (2 weeks) From 7c5b6cc66a2c87dd32d44c9388e948c87d5b220c Mon Sep 17 00:00:00 2001 From: Kimonas Sotirchos Date: Mon, 22 Nov 2021 18:26:30 +0200 Subject: [PATCH 4/5] handbook: Add release selection process Signed-off-by: Kimonas Sotirchos --- releases/handbook.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/releases/handbook.md b/releases/handbook.md index c0c7c4dce..ad2761bb7 100644 --- a/releases/handbook.md +++ b/releases/handbook.md @@ -199,6 +199,22 @@ Criteria for timeline that the team needs to consider * All release team members have the proper permissions and are meeting regularly * A tracking issue for the release has been created in kubeflow/community +#### Release Team Selection + +The leads of the current release team will be selecting their successors for +the next release. This should also take place before the current release team +holds the release retrospective, in order for the new team to be able to +provide feedback. + +The process for selecting shadows and members will be different though. In this +case we want to welcome as many members as possible to join the release team. +The release team should make an outreach via the available channels, +mailing-list, slack, GitHub, and ask for volunteers that would like to +participate in the release team. + +We currently don't have a limit on how many consecutive times someone can be a +release manager, but it is hightly recommended that this role is rotated. This +will allow us to further evolve our process and handbook. ### Development (10 weeks) From 7cf0dd92bdc9bcff4754863bb1a344e022b59477 Mon Sep 17 00:00:00 2001 From: Kimonas Sotirchos Date: Mon, 22 Nov 2021 18:30:48 +0200 Subject: [PATCH 5/5] git: Add a gitignore file for vim Signed-off-by: Kimonas Sotirchos --- releases/.gitignore | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 releases/.gitignore diff --git a/releases/.gitignore b/releases/.gitignore new file mode 100644 index 000000000..3cf2cc662 --- /dev/null +++ b/releases/.gitignore @@ -0,0 +1,7 @@ +# vim +[._]*.s[a-v][a-z] +!*.svg # comment out if you don't need vector files +[._]*.sw[a-p] +[._]s[a-rt-v][a-z] +[._]ss[a-gi-z] +[._]sw[a-p]