Closed
Bug 1388306
Opened 7 years ago
Closed 7 years ago
[tracking bug] what went wrong during 55.0 release day
Categories
(Release Engineering :: Release Automation: Other, enhancement)
Release Engineering
Release Automation: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mtabara, Unassigned)
References
Details
This is to track all the different issues and follow-up that went wrong during release day on 2017-08-08. I'll start filing separately in a bit, one by one.
|
Reporter | |
Comment 1•7 years ago
|
||
Not enough people have access to restart release notifications heroku app. Johan tracks that in bug 1388273.
Depends on: 1388273
|
|
Reporter | |
Comment 2•7 years ago
|
||
WNP is affected during this release because of bug 1301517. It blocked us to complete bug 1386224. However, although it bit us today and yesterday when we attempted to test over in release-cdntest, it may be feature, not a bug afterall. Robert Strong is tracking that work in bug 1388204.
|
|
Reporter | |
Comment 3•7 years ago
|
||
I think we can close this. The only bug remaining is 1388321 which is already tracked as part of rethinking releaseduty under bug 1397840.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•