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.

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

Release 1.13 timeline and schedule #294

Merged
merged 1 commit into from Sep 26, 2018

Conversation

@AishSundar
Contributor

AishSundar commented Sep 14, 2018

Here's a straw-man PR for the 1.13 release schedule. In general the timeline across the calendar quarter for this release is highly crunched due to 2 Kubecons (Shangai, Nov 13-15 and Seattle, Dec 11-13), US Thanksgiving (Nov, 22-23) and the holiday season during last 2 weeks of December.

I have highlighted some main points below in an attempt to explain my rationale around the schedule and welcome any input/feedback:

  • The release cycle length is only 10 weeks long (reasons stated above).
  • Total feature planning and development time are reduced by a week each (both are in keeping with release 1.9, which was also a shorter cycle).
    • Start of release cycle to Feature freeze is 3 weeks vs traditional 4 weeks.
    • Time between Feature freeze and Code freeze is 3.5 weeks vs traditional 4.5 weeks.
  • Code slush and Code freeze will continue to follow a shortened timeframe, of 1 week and 2 weeks respectively, in keeping with 1.11 and 1.12 cycles. But if CI signal is not green as we get toward the intended slush and freeze we may need to elongate them by starting them earlier. This would be communicated early and broadly if it is an incoming risk to the release stability mid-cycle.
  • Code thaw is only 3 days long! This is mainly to get the release out before Kubecon Seattle which falls in the 2nd week of December. Releasing post Kubecon (3rd week of December) will be risky due to contributors' potential unavailability and is also the least preferred option in terms of media attention and PR. Hence, aiming for a release in the 1st week of December will still give us some wiggle room to release during Kubecon in the event of possible slip.

With all that said, feature load and planning by SIGs will play the most crucial factor in keeping this release on track. Delivering features on time with quality will help stabilize CI signal faster and release on time. During the feature definition phase we will meet with SIGs to re-emphasize release cycle length and encourage them to gauge and plan their feature aspirations accordingly. We carry on the past intent to have initial docs drafts as well as test cases arriving in conjunction with the code at or ahead of code freeze.

In the final days of the cycle in an attempt to thaw and stabilize the release sooner we may postpone more incoming cherry picks to the point release depending on risk assessments.

@AishSundar

This comment has been minimized.

Show comment
Hide comment
@AishSundar

AishSundar Sep 14, 2018

Contributor

/hold

Contributor

AishSundar commented Sep 14, 2018

/hold

@AishSundar

This comment has been minimized.

Show comment
Hide comment
@AishSundar
Contributor

AishSundar commented Sep 14, 2018

/cc @kubernetes/sig-release-members

Sig leads:
/cc Jaice Singer DuMars caleb miles

1.12 release team leads
/cc @tpepper @justaugustus @mohammedzee1000 @cjwagner @dougm @guineveresaenger @zparnold @feiskyer @nickchase @kbarnard10

1.13 release team delta vs 1.12
/cc @jberkus @kacole2 @nikopen @tfogo @marpaia @aleksandra-malinowska

@k8s-ci-robot

This comment has been minimized.

Show comment
Hide comment
@k8s-ci-robot

k8s-ci-robot Sep 14, 2018

Contributor

@AishSundar: GitHub didn't allow me to request PR reviews from the following users: caleb, Singer, nikopen, DuMars, miles.

Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @kubernetes/sig-release-members

Sig leads:
/cc Jaice Singer DuMars caleb miles

1.12 release team leads
/cc @tpepper @justaugustus @mohammedzee1000 @cjwagner @dougm @guineveresaenger @zparnold @feiskyer @nickchase @kbarnard10

1.13 release team delta vs 1.12
/cc @jberkus @kacole2 @nikopen @tfogo @marpaia @aleksandra-malinowska

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Contributor

k8s-ci-robot commented Sep 14, 2018

@AishSundar: GitHub didn't allow me to request PR reviews from the following users: caleb, Singer, nikopen, DuMars, miles.

Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @kubernetes/sig-release-members

Sig leads:
/cc Jaice Singer DuMars caleb miles

1.12 release team leads
/cc @tpepper @justaugustus @mohammedzee1000 @cjwagner @dougm @guineveresaenger @zparnold @feiskyer @nickchase @kbarnard10

1.13 release team delta vs 1.12
/cc @jberkus @kacole2 @nikopen @tfogo @marpaia @aleksandra-malinowska

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@AishSundar

This comment has been minimized.

Show comment
Hide comment
@AishSundar

AishSundar Sep 14, 2018

Contributor

/milestone v1.13

Contributor

AishSundar commented Sep 14, 2018

/milestone v1.13

@nickchase

This comment has been minimized.

Show comment
Hide comment
@nickchase

nickchase Sep 14, 2018

Contributor

Maybe I'm nuts for suggesting this, but because it's such a short cycle, and because we will have ~40 new features in 1.12, maybe 1.13 should just focus on stabilizing existing features...?

Contributor

nickchase commented Sep 14, 2018

Maybe I'm nuts for suggesting this, but because it's such a short cycle, and because we will have ~40 new features in 1.12, maybe 1.13 should just focus on stabilizing existing features...?

@idvoretskyi

This comment has been minimized.

Show comment
Hide comment
@idvoretskyi

idvoretskyi Sep 14, 2018

Member

I second @nickchase here. Based on my experience of wrangling the features in Q4'2017, it's the best scenario due to the short release cycle and heavy media attention to the new Kubernetes release during KubeCon.

Member

idvoretskyi commented Sep 14, 2018

I second @nickchase here. Based on my experience of wrangling the features in Q4'2017, it's the best scenario due to the short release cycle and heavy media attention to the new Kubernetes release during KubeCon.

@AishSundar

This comment has been minimized.

Show comment
Hide comment
@AishSundar

AishSundar Sep 14, 2018

Contributor

@nickchase @idvoretskyi I completely agree with you. Infact @justaugustus suggesting the same idea of a stabilization release restricting only to features falling out of 1.12. I am not sure who should to run this by for approval before we make that official. @jdumars and @calebamiles do let us know what you think.

Contributor

AishSundar commented Sep 14, 2018

@nickchase @idvoretskyi I completely agree with you. Infact @justaugustus suggesting the same idea of a stabilization release restricting only to features falling out of 1.12. I am not sure who should to run this by for approval before we make that official. @jdumars and @calebamiles do let us know what you think.

@justaugustus

This comment has been minimized.

Show comment
Hide comment
@justaugustus

justaugustus Sep 14, 2018

Member

Let's make sure we bring this to next SIG Release meeting, Aish.

Member

justaugustus commented Sep 14, 2018

Let's make sure we bring this to next SIG Release meeting, Aish.

@tpepper

Mostly LGTM, aside from a couple small things I noted in particular the blog comment and release-1.9 CI comment.

@AishSundar

This comment has been minimized.

Show comment
Hide comment
@AishSundar

AishSundar Sep 22, 2018

Contributor

@tpepper I have addressed your comments. PTAL

All, I would like to push this draft of the schedule by Thursday 9/27, in time for 1.13 on Monday 10/1. So please provide any feedback by then. Thanks.

Contributor

AishSundar commented Sep 22, 2018

@tpepper I have addressed your comments. PTAL

All, I would like to push this draft of the schedule by Thursday 9/27, in time for 1.13 on Monday 10/1. So please provide any feedback by then. Thanks.

@tpepper

This comment has been minimized.

Show comment
Hide comment
@tpepper

tpepper Sep 24, 2018

Contributor

/lgtm

I'm curious to see if any of the broader SIG leads have any worries, but it seems like a reasonable set of compromises given everything on the calendar this last quarter of 2018!

Contributor

tpepper commented Sep 24, 2018

/lgtm

I'm curious to see if any of the broader SIG leads have any worries, but it seems like a reasonable set of compromises given everything on the calendar this last quarter of 2018!

| Docs deadline - Open placeholder PRs | Docs Lead | | 8 | | | | |
| All release-1.13 CI jobs/testgrid created | Test Infra Lead | | 9 | | | | |
| Begin Code Slush | Bot, Lead | | 9 | | | week 6 | |
| All Issues & PRs must have complete labels | Bug Triage | | 12 | | | week 7 | |

This comment has been minimized.

@spiffxp

spiffxp Sep 24, 2018

Member

I know it's not technically release related, but I wonder if it would be worth explicitly adding some rows in here to remind people when the following are happening:

  • Kubecon Shanghai (Nov 13-15)
  • US Thanksgiving (Nov 22)
  • Contributor summit + Kubecon Seattle (Dec 9-13)
@spiffxp

spiffxp Sep 24, 2018

Member

I know it's not technically release related, but I wonder if it would be worth explicitly adding some rows in here to remind people when the following are happening:

  • Kubecon Shanghai (Nov 13-15)
  • US Thanksgiving (Nov 22)
  • Contributor summit + Kubecon Seattle (Dec 9-13)

This comment has been minimized.

@AishSundar

AishSundar Sep 24, 2018

Contributor

done

@AishSundar

AishSundar Sep 24, 2018

Contributor

done

@jberkus

This comment has been minimized.

Show comment
Hide comment
@jberkus

jberkus Sep 24, 2018

Contributor

/lgtm

Contributor

jberkus commented Sep 24, 2018

/lgtm

@cjwagner

This comment has been minimized.

Show comment
Hide comment
@cjwagner

cjwagner Sep 24, 2018

Member

bump for tide?

Member

cjwagner commented Sep 24, 2018

bump for tide?

@k8s-ci-robot k8s-ci-robot removed the lgtm label Sep 24, 2018

@AishSundar

This comment has been minimized.

Show comment
Hide comment
@AishSundar

AishSundar Sep 24, 2018

Contributor

@spiffxp added the Kubecons and Thanksgiving into the schedule.

@tpepper @jberkus @spiffxp need LGTM again plz

Contributor

AishSundar commented Sep 24, 2018

@spiffxp added the Kubecons and Thanksgiving into the schedule.

@tpepper @jberkus @spiffxp need LGTM again plz

@jberkus

This comment has been minimized.

Show comment
Hide comment
@jberkus

jberkus Sep 24, 2018

Contributor

/lgtm

Contributor

jberkus commented Sep 24, 2018

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm label Sep 24, 2018

@spiffxp

This comment has been minimized.

Show comment
Hide comment
@spiffxp

spiffxp Sep 25, 2018

Member

/lgtm

Member

spiffxp commented Sep 25, 2018

/lgtm

@jdumars

This comment has been minimized.

Show comment
Hide comment
@jdumars

jdumars Sep 26, 2018

Member

/lgtm

Member

jdumars commented Sep 26, 2018

/lgtm

@tpepper

This comment has been minimized.

Show comment
Hide comment
@tpepper

tpepper Sep 26, 2018

Contributor

/lgtm

Contributor

tpepper commented Sep 26, 2018

/lgtm

@k8s-ci-robot

This comment has been minimized.

Show comment
Hide comment
@k8s-ci-robot

k8s-ci-robot Sep 26, 2018

Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AishSundar, jberkus, jdumars, spiffxp, tpepper

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [AishSundar,jberkus,jdumars,spiffxp,tpepper]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Contributor

k8s-ci-robot commented Sep 26, 2018

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AishSundar, jberkus, jdumars, spiffxp, tpepper

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [AishSundar,jberkus,jdumars,spiffxp,tpepper]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@AishSundar

This comment has been minimized.

Show comment
Hide comment
@AishSundar

AishSundar Sep 26, 2018

Contributor

/hold cancel

Thanks all for the review, getting this in now

Contributor

AishSundar commented Sep 26, 2018

/hold cancel

Thanks all for the review, getting this in now

@k8s-ci-robot k8s-ci-robot merged commit 3675848 into kubernetes:master Sep 26, 2018

2 checks passed

cla/linuxfoundation AishSundar authorized
Details
tide In merge pool.
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment