MozillaZine

The first official 20180307 builds are out

Discussion about official Mozilla Firefox builds
Josa
 
Posts: 2975
Joined: July 28th, 2009, 4:52 pm

Post Posted March 6th, 2018, 10:11 am

Previous Nightly Builds thread 20180306

The first official 20180307 NIGHTLY builds are out
.The Official Firefox 59 RC 2 builds are not yet out

Previous NIGHTLY: 20180306 (Fx 60.0a1)
Previous BETA: 20180306 (Fx 59.0 RC1)

Mozilla Inbound Builds
Treeherder
Release Notes: NIGHTLY | BETA
Changelogs: NIGHTLY | BETA


Fixed:
    NIGHTLY +29
  1. #1414901
  2. #1440402
  3. #1440627
  4. #1442984
  5. #1443528 [Core:Audio/Video: cubeb]-Extend Telemetry::AUDIOSTREAM_BACKEND_USED telemetry probe [Uns][]
  6. #1443368 [Core:Audio/Video: cubeb]-PulseRust backend asserts that 'assertion failed: `(left != right)`' [Uns][]
  7. #1443205 [Core:CSS Parsing and Computation]-Convert the media feature constants to enum classes. [Uns][]
  8. #1442523 [Core:Disability Access APIs]-Deadlock on content process with a11y [Win][]
  9. #1363862 [Core:Internationalization]-Add a chrome-only DOM API for localization [Uns][]
  10. #1438608 [Core:Internationalization]-Missing strings are overreported ("L10nError: Unknown message") [Uns][]
  11. #1443402 [Core:Layout]-Fix some -Wmissing-prototypes warnings in layout [Uns][]
  12. #1442627 [Core:Panning and Zooming]-Reduce usage of APZCTreeManager class in the codebase [Uns][]
  13. #1434439 [Core:WebRTC: Audio/Video]-Firefox can get stuck in mode where it always downscales camera video unnecessarily. [All][]
  14. #1280099 [Core:WebRTC: Audio/Video]-Intermittent test_peerConnection_trackDisabling.html | Test timed out. [Uns][]
  15. #1436074 [Core:WebRTC: Audio/Video]-Reduce timer for turning off camera on disable by time camera has already been on [Uns][]
  16. #1436694 [Core:WebRTC: Audio/Video]-SourceListener in bad state after initial Start() fails [Uns][]
  17. #1362303 [Core:Widget: Cocoa]-Crash in IPCError-browser | SHMEM_CREATED_MESSAGE Payload error: message could not be deserialized [Mac][tpi:+]
  18. #1440146 [Core:XP Toolkit/Widgets: XUL]-Remove unused menubutton-item binding [Uns][[xbl-available]]
  19. #1437803 [Firefox:Address Bar]-Add telemetry to understand how many users use TAB to cycle through Address Bar results [Uns][[fxsearch]]
  20. #1443229 [Firefox:Address Bar]-Address bar shows search suggestions even when "Show search suggestions in address bar results" is unchecked [Uns][]
  21. #1440644 [Firefox:Bookmarks & History]-The New Bookmark dialog/window doesn't save the keyword [All][[fxsearch]]
  22. #1443193 [Firefox:Developer Tools: Debugger]-Debugger should not include babel-traverse [Uns][]
  23. #1401847 [Firefox:Developer Tools: Inspector]-Layout Grid colors should be restored after reload, even if grid is unchecked [Uns][[DevRel:P1]]
  24. #1421387 [Firefox:Developer Tools]-Change "Style sheet could not be loaded” Red Error Banner to a Neutral Warning Banner [Uns][]
  25. #1443453 [Firefox:Tabbed Browser]-Stop loading tabbrowser.css a second time in the tabbrowser-tabs and tabbrowser-tab bindings [All][]
  26. #1402845 [Firefox:Theme]-When uBlock, NoScript and other browserAction buttons are in the overflow menu, their panel is shown with wrong size and with a "two step resizing" [Uns][[reserve-photon-structure]]
  27. #851471 [Toolkit:Downloads API]-Decommission nsIDownloadManager [All][[tracking]]
  28. #1434483 [Toolkit:Form Autofill]-Rename profileStorage singleton to formAutofillStorage to make it more clear [All][[form autofill:tech-debt][lang=js]]
  29. #1443371 [Toolkit:View Source]-Clean up unused message listeners, code paths after bug 1418403 [Uns][]

    Partial Landings/Diagnostic Patches:
    None

    RC 1 -> RC 2 Changelog +1
  1. #1443229 [Firefox:Address Bar]-Address bar shows search suggestions even when "Show search suggestions in address bar results" is unchecked [Uns][]

Nightly 60 fixes since 20180122 (Gecko 59) ~1824
Beta 59 fixes since 20171113 (Gecko 58) ~2623

Nightly Blog
Release Calendar
Release Tracking
MozRegression Guide
Last edited by Josa on March 7th, 2018, 10:20 am, edited 1 time in total.

WaltS48

User avatar
 
Posts: 3599
Joined: May 7th, 2010, 9:38 am
Location: Pennsylvania, USA

Post Posted March 6th, 2018, 11:02 am

The Official 60.0b1 Developer Edition is out.
Linux Desktop - AMD Athlon(tm) II X3 455 3.3GHz | 8.0GB RAM | GeForce GT 630
Windows Notebook - AMD A8 7410 2.2GHz | 6.0GB RAM | AMD Radeon R5

Mark12547
 
Posts: 186
Joined: May 13th, 2017, 11:36 am
Location: Oregon, United States, Earth

Post Posted March 6th, 2018, 12:48 pm

WaltS48 wrote:The Official 60.0b1 Developer Edition is out.


Also, the Beta version now updates to 59.0 (no indication in version number that it is beta) when one does Help -> About Firefox.

I haven't been watching the Rapid Release Calendar and it snuck up on me: we are a week away from official rolling of versions down the channels.

tomatoshadow2

User avatar
 
Posts: 190
Joined: May 11th, 2017, 9:52 am

Post Posted March 6th, 2018, 1:43 pm

Isn't Beta usually labeled the same or am I mistaken?

Mark12547
 
Posts: 186
Joined: May 13th, 2017, 11:36 am
Location: Oregon, United States, Earth

Post Posted March 6th, 2018, 6:05 pm

tomatoshadow2 wrote:Isn't Beta usually labeled the same or am I mistaken?


Yes, usually Beta and Developer show the same version numbers and maintenance is applied to both at the same time. (Nightly=60.0a1; Beta=Developer=59.0b__; Release=58.0.2)

But the exception is during the week or so leading up to code rolling into the next channel.

During the week preceding the roll, Developer is used for taking what was in Nightly(60.0a1), and cleaning it up to become Beta (60.0b1) but, because it is the Developer channel, will have developer-friendly tweaks. There may be two or three point upgrades in Developer before that code is available in both Developer and Beta.

Meanwhile the Beta channel (was 59.0b__) is being used to clean up the code for Release. This is the last bit that cleans up versions and branding to reflect that it is Release (59.0, though there can be several 59.0's without visible change of version number if issues are found while getting Beta ready for Release).

At this point: Nightly=60.0a1, Developer=60.0b1, Beta=59.0, Release=58.0.2.

Then when Beta is suppose to receive the new version next week, it will get a copy of the Developer code, minus the tweaks that make Developer developer-friendly. Likewise, Release will receive the code that was in Beta with as few changes as possible. Likewise, at some point Nightly will be re-versioned to the next version number, though when this is done usually the only change the first night is just the version number.

So, after the roll, Nightly=61.0a1, Developer=Beta=60.0b3 (if two additional updates are needed to get code ready for Beta), and Release=59.0.

Josa
 
Posts: 2975
Joined: July 28th, 2009, 4:52 pm

Post Posted March 7th, 2018, 10:20 am


Return to Firefox Builds


Who is online

Users browsing this forum: Glibnes and 3 guests