Closed Bug 1150126 Opened 11 years ago Closed 11 years ago

Thunderbird download page shows 31.5.0, should show 31.6.0

Categories

(www.mozilla.org :: Product Details, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: raysatiro, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:39.0) Gecko/20100101 Firefox/39.0 Build ID: 20150330030203 Steps to reproduce: https://www.mozilla.org/en-US/thunderbird/download https://www.mozilla.org/en-US/thunderbird/all.html Actual results: Should show 31.6.0 since 2015-03-31 but still shows 31.5.0 Expected results: Should show 31.6.0
Severity: normal → major
This might not be shipped yet, I can't remember.
Component: Releases → Pages & Content
Flags: needinfo?(vseerror)
Product: Release Engineering → www.mozilla.org
QA Contact: rail
About Thunderbird still says 31.5.0 is up-to-date.
Component: Pages & Content → Product Details
I see this also. I think sylvestre or releng still has steps to do. The last emails on thunderbird-drivers are 9:34am bhearsum pushing to mirrors 9:53am Joe: "QA signoff on cdn testing" (EST times) (In reply to Kohei Yoshino [:kohei] from comment #2) > About Thunderbird still says 31.5.0 is up-to-date. comment 0: > https://www.mozilla.org/en-US/thunderbird/download > https://www.mozilla.org/en-US/thunderbird/all.html
Flags: needinfo?(vseerror) → needinfo?(sledru)
Product detail updated by r139862 I don't know how often it is refreshed.
Flags: needinfo?(sledru)
(In reply to Sylvestre Ledru [:sylvestre] from comment #4) > Product detail updated by r139862 > I don't know how often it is refreshed. Push to mirrors occurred, and QA signed off. The public bits are still old. Is the next step "push Thunderbird 31.6.0 build 1 to the release channel <eom>" ?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(sledru)
Pfff, I sent this email. I guess it was in the g* black hole... resent.
Flags: needinfo?(sledru)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.