Google 1.17.1 follow-up issues go into 1.18.1 - but nobody works the weekend for them

November 9, 2026 at 4:04 PMoperationallow

Situation

On Friday 11/6 Tissa sent three issues found in 1.17.1, including the multipath dracut module breaking boot in the hotfix images, and asked that they be addressed in 1.18.1. Peter forwarded them to Justin and Nathan: make sure these get touched in 1.18.1, but not something folks should work the weekend for. When Justin confirmed he had passed it on, Peter checked: including not this weekend?

Reasoning

Confirmed by Peter. The contract had just started moving, a finished 1.18.1 was in hand, and the new issues were refinements rather than outages. Having just thanked the team in person for weekend and holiday work, letting a Friday customer email trigger another weekend would undo it; the follow-up check shows he expected the default to be working through. A non-emergency customer issue waits for working hours, even for the largest customer.

Additional Context

Connects to the 11/3 note to Bjorn that the team is burned out.

Observed Evidence

Forward to Justin and Nathan with the no-weekend instruction; follow-up check that the no-weekend part was passed on.

Confidence Breakdown

33/35
Evidence
14/30
Pattern
16/20
Source
7/15
Corroboration

Reasoning Depth Analysis

Org Signal:Peter protects weekends explicitly when urgency is gone.
Who Affected:Linux and RAT engineers on the Google work.
Precedent:Non-emergency customer asks wait for working hours.
Consequences:Slight delay on 1.18.1 refinements.
Timing:Friday afternoon email after the contract started moving.

Source

reflection

AI Confidence

70%

Related Context

📧
Fwd: 1.17.1 path forward

email

Let us make sure these get touched in 1.18.1. But not something folks should work the weekend for.

📧
Re: 1.17.1 path forward

email

Including not this weekend?

Outcome

No outcome recorded yet.

Decision ID: 50924e3f-266c-4151-a70d-8a4cb38fbaf2