sig-release icon indicating copy to clipboard operation
sig-release copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

1.22 updates to Branch Manager handbook

Open puerco opened this issue 3 years ago • 24 comments

What would you like to be added:

Derived from the branch management activities during the v1.22 cycle, it became evident that we need to add some information to the Branch Manager handbook:

  • [x] After 1.21, Release Engineering acquired the responsibility of updating the publishing bot rules. This time @palnabarun noted we were leaving out the update and PRd the rules for 1.22. We need to add this process to the rules. Note that there is a command in the works to automate the rules. This update is currently in flight (https://github.com/kubernetes/sig-release/pull/1504 @xmudrii ).
  • [x] Fast Forwarding the branch is no longer the way we even out branches between code freeze and release (we now do cherry picks). The manual has still in it a section about krel ff and fast forwarding the branch (https://github.com/kubernetes/sig-release/pull/2091).
  • [ ] The instructions for generating the new branch jobs do not work as they are. This could be due to a bug in the script or because of something missing from the instructions, we need to investigate and update the manual accordingly (replaced with https://github.com/kubernetes/sig-release/issues/2227).
  • [x] There is a link titled "Update Slack branch whitelists" in the manual under During the release creation. The section was removed but the link is there (https://github.com/kubernetes/sig-release/pull/2091).
  • [ ] During the last couple of releases, the branch management team has started the practice of running the mocks the night before release day. This practice has many benefits such as giving the releng team a chance to deal with problems in the tooling without delaying the release and finishing the release process earlier allowing for teams in other time zones to finish during their daytime. We should add this practice as current to the handbook.

Why is this needed:

These updates are needed to reflect the current way we run a release cycle.

/kind documentation /milestone v1.23

puerco avatar Aug 05 '21 00:08 puerco

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Nov 03 '21 01:11 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Nov 03 '21 08:11 xmudrii

/assign (I will have a look at documenting some of these gotchas before the 1.23 RC)

palnabarun avatar Nov 15 '21 07:11 palnabarun

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Feb 13 '22 08:02 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Feb 13 '22 12:02 xmudrii

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Jun 21 '22 13:06 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Jun 22 '22 07:06 xmudrii

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Sep 20 '22 08:09 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Sep 20 '22 08:09 xmudrii

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Dec 19 '22 08:12 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Dec 19 '22 09:12 xmudrii

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Mar 19 '23 10:03 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Mar 19 '23 18:03 xmudrii

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Jun 17 '23 18:06 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Jun 19 '23 10:06 xmudrii

/assign

sarthaksarthak9 avatar Aug 01 '23 17:08 sarthaksarthak9

@puerco I think the fourth checklist is also solved. I try to find the link but it is not present there

sarthaksarthak9 avatar Aug 02 '23 05:08 sarthaksarthak9

@sarthaksarthak9 Thank you for bringing it up, it's fixed by https://github.com/kubernetes/sig-release/pull/2091. I updated the checklist to reflect this.

xmudrii avatar Aug 02 '23 08:08 xmudrii

@sarthaksarthak9 Thank you for bringing it up, it's fixed by #2091. I updated the checklist to reflect this.

I also try to solved the second checklist could you pls review the changes #2299

sarthaksarthak9 avatar Aug 02 '23 10:08 sarthaksarthak9

@sarthaksarthak9 I think only the last item in the checklist is relevant for now. Instructions for generating branch jobs also need update, but that is something that should be done by Release Managers because of insights into the process.

xmudrii avatar Aug 02 '23 10:08 xmudrii

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Jan 25 '24 17:01 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Jan 25 '24 18:01 xmudrii