Sig-release: Add information about what qualifies for a milestone

[justaugustus]

/sig release
/help

rel: https://github.com/kubernetes/community/pull/2408

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[spiffxp]

/remove-lifecycle stale
/milestone v1.14

Let's quantify this as part of the v1.14 release cycle

There are multiple repos that now have a v1.14 milestone, I believe the ones we care about are:

• kubernetes/enhancements: tracking issues that correspond to large KEP-driven enhancements to kubernetes
• kubernetes/kubernetes: all of the sundry bugs and implementation issues for the k/k codebase
• kubernetes/sig-release: release-team tasks, milestones, and process improvements to be implemented during the v1.14 release cycle
• kubernetes/website: is its own beast and I will defer to sig-docs until I have a better grasp of their process

IMO all issues that relate to code or tasks or process for v1.14 should have an associated milestone, regardless of repo.

For PRs, I care only about code that lands _in_ the release, so kubernetes/kubernetes. I am less concerned with their use in the first half of the release, but consider them mandatory in the latter half once we enter the burndown phase (code slush, code freeze, code thaw). This is to help us keep track of all work destined to land in the release.

It might be nice if we could have automation auto-milestone is:pr base:master repo:kubernetes/kubernetes with v1.14 for the first half of the release lifecycle.

ref: https://github.com/kubernetes/sig-release/issues/243#issuecomment-409391292 for the summary of our discussion of hopes and dreams on this during a sig-release meeting, there may be others

[spiffxp]

/milestone v1.14

[spiffxp]

/kind documentation

[justaugustus]

Anyone interested in doc-ing this?

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[justaugustus]

/remove-lifecycle stale
/priority important-soon
/milestone v1.15

[justaugustus]

/area release-team
/milestone v1.16

[jeefy]

/assign

[guineveresaenger]

Thanks for working on this, Jeff!

[guineveresaenger]

/remove-help

[tpepper]

I've added some words via a PR in the community repo https://github.com/kubernetes/community/pull/4081 regarding how we review cherry-pick PRs for inclusion on a milestone's release-X.Y branch.

[alejandrox1]

/milestone v1.17

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[alejandrox1]

/remove-lifecycle stale
/milestone v1.18
/assign @onlydole

[alejandrox1]

@onlydole may be useful to chat with bug triage people. would be useful to sync whatever info we end up adding here with the bug triage handbook

[onlydole]

@smourapina - could I sync with you and the team this week on this issue?

[smourapina]

Sure @onlydole, let's do that!

[markyjackson-taulia]

I sent over the initial draft to @onlydole of items from a bug-triage perspective

[markyjackson-taulia]

cc @onlydole
Per v1.18 release meeting adding the google doc here:
https://docs.google.com/document/d/1vEycLfyNDO95O6qIx1bsYaQWYCHYFgAOK6DNdBy_aPM/edit

[onlydole]

Talking more with @tpepper, we need to focus on two primary paths:

1. Release team side of things (or triage or CI signal, review/approver/OWNER, etc): put guidance in the role handbooks so they can operationalize what’s expected of their role

2. PR / cherry pick submitter: put guidance in https://github.com/kubernetes/community/blob/master/contributors/devel/sig-release/cherry-picks.md so they know what’s expected of them for their change to merge

I'll update this PR with changes more in-line with those two focuses

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[onlydole]

/remove-lifecycle rotten

[LappleApple]

Hey @onlydole, are you still actively working on this?

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[onlydole]

Howdy, @LappleApple! I was on a holding pattern for this, and I don't think there's a clear way forward on this issue. I'd like to bring it up on the next release engineering meeting as a topic to see how we could close this out!

/remove-lifecycle stale

[LappleApple]

Awesome, @onlydole! Go ahead and add to the meeting agenda as your time and schedule allow :)

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[onlydole]

/close in favor of https://github.com/kubernetes/sig-release/issues/1257