Closed Bug 1389643 Opened 8 years ago Closed 8 years ago

Earlybird/aurora users are stranded on 54.0a2 (2017-06-20) (64-bit) - we should upgrade them to more-recent Beta builds

Categories

(Thunderbird :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1366893

People

(Reporter: dholbert, Unassigned)

Details

I just realized I haven't been receiving updates to my Thunderbird for quite a while -- I was an Earlybird user (not quite gutsy enough for Nightly), and it seems I'm now stuck on Earlybird 54.0a2 (2017-06-20) (64-bit), a build from nearly 2 months ago. It looks like this was the last "aurora" build that was produced -- if I skim this page... https://ftp.mozilla.org/pub/thunderbird/nightly/2017/06/ ...the last "comma-aurora" line is 2017-06-20-00-40-06-comm-aurora I'm guessing this all has to do with "Project Dawn" elimination of the Aurora development channel. Still: we should not leave this channel's users stranded on the final Aurora build that was produced! We should upgrade them to Beta, probably -- that's what happened for Firefox aurora users. And it's still what happens if I download an old Firefox aurora build and check for updates -- I get safely updated to the latest beta version (with DevEdition branding). But for Earlybird, I only get updated as far as June 20th and then I'm left stranded.
Component: Disability Access → General
Summary: Earlybird users are stranded on 54.0a2 (2017-06-20) (64-bit) → Earlybird users are stranded on 54.0a2 (2017-06-20) (64-bit) - we should upgrade them to more-recent Beta builds
(You can reproduce this by downloading an aurora build from the ftp.m.o URL in comment 0, and running it with a fresh thunderbird profile [if you like], and doing Help|About to force an update check.)
This is blocked on Bug 1366893
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Summary: Earlybird users are stranded on 54.0a2 (2017-06-20) (64-bit) - we should upgrade them to more-recent Beta builds → Earlybird/aurora users are stranded on 54.0a2 (2017-06-20) (64-bit) - we should upgrade them to more-recent Beta builds
Thanks. Glad to see there's recent activity there.
You need to log in before you can comment on or make changes to this bug.