Skip to content
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

Remove code slush #442

Merged

Conversation

spiffxp
Copy link
Member

@spiffxp spiffxp commented Jan 12, 2019

We decided a clear warning to brace for code freeze was sufficient,
and a whole extra delineated phase wasn't worth the effort. We'll
still remind folks not to do mean things like land massive changes
or refactors N days before code freeze.

ref: #269

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 12, 2019
@k8s-ci-robot k8s-ci-robot added the sig/release Categorizes an issue or PR as relevant to SIG Release. label Jan 12, 2019
@spiffxp
Copy link
Member Author

spiffxp commented Jan 12, 2019

/hold
for comment (also, ref: kubernetes/community#3090)

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 12, 2019
@justaugustus
Copy link
Member

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 12, 2019
@spiffxp
Copy link
Member Author

spiffxp commented Jan 14, 2019

I vastly underestimated how many times the word "slush" is mentioned in playbooks. The following playbooks need an update:

  • test-infra
  • bug-triage
  • release-notes
  • branch-manager
  • release-team-lead
  • ci-signal
  • enhancements

I would rather hold this to take an initial pass

@tpepper
Copy link
Member

tpepper commented Jan 14, 2019

I'm also in favor of this, but definitely would prefer removal across the board so will await the amended commit / PR.

We decided a clear warning to brace for code freeze was sufficient,
and a whole extra delineated phase wasn't worth the effort. We'll
still remind folks not to do mean things like land massive changes
or refactors N days before code freeze.
@spiffxp spiffxp force-pushed the no-more-code-slush-only-ned-stark branch from ef8b5c4 to cf0399c Compare January 15, 2019 00:35
@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 15, 2019
@spiffxp
Copy link
Member Author

spiffxp commented Jan 15, 2019

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 15, 2019
I traded Slush for Burndown in the context of daily duties
being ramped up a week before code freeze
This was the toughest to change, I feel like it needs more
of a rewrite from the Bug Triage folks. Tons of text, and
more phases than the actual release cycle. It also talked
about Burndown solely during the last week, which isn't
quite true.

In the context of duties changing as phases change, I
changed "Slush" to "Burndown", and also changed
"Release Burndown" to "Code Thaw"
@spiffxp spiffxp force-pushed the no-more-code-slush-only-ned-stark branch from cf0399c to 3a97133 Compare January 15, 2019 00:44
@justaugustus
Copy link
Member

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 15, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jdumars, justaugustus, spiffxp

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:

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

@k8s-ci-robot k8s-ci-robot merged commit 785722c into kubernetes:master Jan 15, 2019
@spiffxp spiffxp deleted the no-more-code-slush-only-ned-stark branch January 15, 2019 01:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/release Categorizes an issue or PR as relevant to SIG Release. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants