-
Notifications
You must be signed in to change notification settings - Fork 381
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
Remove code slush #442
Conversation
/hold |
/lgtm |
I vastly underestimated how many times the word "slush" is mentioned in playbooks. The following playbooks need an update:
I would rather hold this to take an initial pass |
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.
ef8b5c4
to
cf0399c
Compare
/hold cancel |
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"
cf0399c
to
3a97133
Compare
/lgtm |
[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 |
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