Closed Bug 1263565 Opened 10 years ago Closed 9 years ago

Release Notes link in Thunderbird 38.7.2 doesn't work

Categories

(Thunderbird :: General, defect)

38 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: tkloepfer, Assigned: Fallen)

Details

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 Build ID: 20160315153207 Steps to reproduce: go to menue -> help -> release notes Actual results: browser opens 'mozilla whooops' error message: https://www.mozilla.org/en-US/thunderbird/nightly/releasenotes/?uri=/thunderbird/releasenotes/&locale=en-US&version=38.7.2&os=WINNT&buildid=20160402193654 Expected results: show release notes in browser
confirmed Odd, because fallen had written on 4/7 Taken care of p-d for both releases: p-d: r150593 thunderbird: r150594 Can't say I tested it.
Status: UNCONFIRMED → NEW
Ever confirmed: true
(get thee out of Untriaged!)
Component: Untriaged → General
This is working for me now.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Oh sorry, I was testing my 45.0. The link in Comment 0 is still broken.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to TomKlopf from comment #0) > Actual results: > > browser opens 'mozilla whooops' error message: > https://www.mozilla.org/en-US/thunderbird/nightly/releasenotes/?uri=/ > thunderbird/releasenotes/&locale=en-US&version=38.7. > 2&os=WINNT&buildid=20160402193654 A little confusion on my side. Is 38.7.2 broken or 45.0? This should be e.g. https://www.mozilla.org/en-US/thunderbird/release/releasenotes/?uri=/thunderbird/releasenotes/&locale=en-US&version=45.0 1) if this is 45.0, why does it say 38.7.2 ? 2) in both cases, why does it use the /nightly/ component?
Thunderbird 38.7.2 is broken, not sure why "45.0" is mentioned
Thanks for the update. I've fixed this in r150621, it should be available after caching has caught up.
Assignee: nobody → philipp
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.