Closed
Bug 1388207
Opened 8 years ago
Closed 7 years ago
Show release ETA on lists of Reviewed and Running/Complete releases
Categories
(Release Engineering :: Applications: Shipit, enhancement, P2)
Release Engineering
Applications: Shipit
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: nthomas, Unassigned)
References
Details
(Whiteboard: [releaseduty])
When you create a build2 or higher it's helpful to know what RelMan has set for build1's release ETA. We don't currently expose this in the list of Reviewed or Running/Complete releases, so you have go digging in release runner log or similar.
Comment 1•8 years ago
|
||
:jcristau added logic[1] to make this visible while the release is in the Submitted section. E.g for 55.0build3 is currently shows:
Mozilla Revision: 9e30e915f1325f041d01c722bd640300f32dc9c3
Mozilla Relbranch: None
L10n Changeset
ETA: 2017-08-08T10:00:00+00:00 <---- ..........
Partial versions: 55.0b13build1,54.0.1build1,54.0build3
Update prompt wait time: Default
Mozharness changeset:
Might be worth extending that behavior a bit to the table as well as a new column so that it's easier to track once it's been successfully submitted and it's part of the "Running/Completed" section.
[1]: https://github.com/mozilla-releng/ship-it/pull/183
Priority: -- → P2
Whiteboard: [releaseduty]
Updated•8 years ago
|
Priority: P2 → P1
Updated•7 years ago
|
Priority: P1 → P2
Comment 2•7 years ago
|
||
Since we're transitioning towards Ship-it v2, I don't think this is valid any longer.
Feel free to reopen if I missed anything.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
| Assignee | ||
Updated•4 years ago
|
Component: Applications: ShipIt (backend) → Applications: ShipIt
You need to log in
before you can comment on or make changes to this bug.
Description
•