The Official 20170625 builds are out

[Josa]

Previous Nightly Builds thread 20170624

The Official 20170625 NIGHTLY builds are out
.The Official Firefox 55 Beta 5 builds are not yet out

Previous NIGHTLY: 20170624 (Fx 56.0a1)
Previous BETA: 20170624 (Fx 55.0b4)

Tinderbox Builds
Treeherder
Release Notes: NIGHTLY | BETA
Changelogs: NIGHTLY | BETA


Fixed:

1. NIGHTLY +0
   None

1. Partial Landings/Diagnostic Patches:
   None

1. Beta 4 -> Beta 5 Changelog +5
2. #1373663
3. #1354933 [Core:Layout: View Rendering]-assert frame pointer is null in view destructor [Uns][]
4. #1374289 [Core:Plug-ins]-clicktoactivate rollout addon: branches "user-changed-from-user-changed-from-control" and " user-changed-from-user-changed-from-test" [Uns][]
5. #1358898 [Toolkit:Async Tooling]-Many intermittent crashes in RunWatchdog [All][[stockwell fixed:product]]
6. #1373293 [Toolkit:WebExtensions: Untriaged]-MatchPattern exception on chrome://favicon/ [Uns][[triaged]]
   None

Nightly 56 fixes since 20170613 (Gecko 55) ~680
Beta 55 fixes since 20170306 (Gecko 54) ~5012

Nightly Blog
Release Calendar
Release Tracking
MozRegression Guide

[avada]

Did v55 beta start hanging Windows' shutdown sequence for anyone else. Every single time... Windows waits for FF to close but it never does.

[DN123ABC]

Silly question. On one computer, I had a version 56 "Nightly" build running a month ago, before there were some big changes with the way builds were done. Since then, I've got a new installation on a newer computer (from XP 32 bit to Win7 64 bit), and put Firefox "beta" version 55 on it. I then brought over my old profile, but it stayed at "beta" version 55. I thought for some reason that it would go out and update to start using the "Nightly" builds again. I don't know if I want to be on the "bleeding edge", and am wondering if there is an intermediate type of build, or is it either/or with just choice of "beta" or "nightly". Also, so far, the profile seems to work, so I don't think there are backwards compatibility issues, at least that I have seen.

So, what advice might folks have, if I want to help test and enjoy some newer features, without being out on the fringes of new stuff that breaks browsing horribly? Thanks.

[malliz]

For you? Stick with releases

[Omega X]

I agree with malliz. Releases happen so often that you'll always see something new.

[avada]

#1374289 [Core:Plug-ins]-clicktoactivate rollout addon: branches "user-changed-from-user-changed-from-control" and " user-changed-from-user-changed-from-test" [Uns][]

Does anyone understand what this bug that landed on beta is about?
What is there even to "roll out" when it comes to click-to-play? It exists for several years now.

[malliz]

Looks like once the user has decided if they want a particular click to play state the browser will no longer ask/look for an event?
Just my reading of it

[WaltS48]

Linux Nightly is out.

Mozilla/5.0 (X11; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0 ID:20170625100343 CSet: c01aa84ded7eb0b3e691f8bcc5cd887c960a779e

[WildcatRay]

Win64 Nightly is out: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 ID:20170625030210 CSet: c01aa84ded7eb0b3e691f8bcc5cd887c960a779e

[DN123ABC]

Let me re-ask my question. Is there a point in the not so distant future, where version 56 will become the "beta" build?

[Tomatoshadow2]

Is there a reason the Mac build of Nightly isn't out yet?

[winapp2]

Let me re-ask my question. Is there a point in the not so distant future, where version 56 will become the "beta" build?

https://wiki.mozilla.org/RapidRelease/Calendar

[toolong]

Let me re-ask my question. Is there a point in the not so distant future, where version 56 will become the "beta" build?

If the release schedule does not slip it should be early August.

[mak77]

@avada re: windows 10 shutdown prevented: https://bugzilla.mozilla.org/show_bug.cgi?id=1374038

[GHM113]

Silly question. On one computer, I had a version 56 "Nightly" build running a month ago, before there were some big changes with the way builds were done.
So, what advice might folks have, if I want to help test and enjoy some newer features, without being out on the fringes of new stuff that breaks browsing horribly? Thanks.

I personally use Nightly as my primary browser and Beta aka DevEdition as a backup when Nightly brakes. That doesn't happen often, though. Completely happy with this setup, so many upcoming features this year: OOP WebExtensions, WebRender, 1st-priority input events, Photon, low priority of the content processes that are not running a foreground tab, NoScript 10, etc