Skip to content

Commit

Permalink
Address review comments
Browse files Browse the repository at this point in the history
Signed-off-by: Furkat Gofurov <[email protected]>
  • Loading branch information
furkatgofurov7 committed Oct 25, 2023
1 parent 15f3ef9 commit 0d210f6
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 2 deletions.
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@
cmd/clusterctl/clusterctl
bin
hack/tools/bin
vars.sh

# Test binary, build with `go test -c`
*.test
Expand Down
4 changes: 2 additions & 2 deletions docs/release/release-team.md
Original file line number Diff line number Diff line change
Expand Up @@ -103,8 +103,8 @@ Before you volunteer to be part of a CAPI release team, please make certain that

## Suggestions for Team Leads

* In the first week of the release cycle, organize an onboarding session with shadows of your team (i.e CI Lead with CI team shadows) to go over the general responsibilities and expectations.
* Clearly communicate with the team shadows you are responsible for, that the majority of the work during the release cycle will be a collaborative effort.
* In the first week of the release cycle, organize an onboarding session with members of your team (i.e CI Lead with CI team members) to go over the general responsibilities and expectations.
* Clearly communicate with the team members you are responsible for, that the majority of the work during the release cycle will be a collaborative effort.
* Establish an ownership rotation policy in consultation with respective team members.
* Provide opportunities for team members to take the lead in cutting a release within the cycle, based on feasibility.
* Define backup ownership and tasks for team members, such as:
Expand Down

0 comments on commit 0d210f6

Please sign in to comment.