MozillaZine

The first official 20180204 builds are out

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

Post Posted February 3rd, 2018, 7:54 am

Previous Nightly Builds thread 20180203

The first official 20180204 NIGHTLY builds are out
.The Official Firefox 59 Beta 7 builds are not yet out

Previous NIGHTLY: 20180203 (Fx 60.0a1)
Previous BETA: 20180202 (Fx 59.0b6)

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


Fixed:
    NIGHTLY +7
  1. #1421568 [Core:DOM]-Add a ChromeOnly method to access also closed shadow roots [Uns][]
  2. #1430303 [Core:DOM: Core & HTML]-Implement ShadowRoot.pointerLockElement [Uns][]
  3. #1435200 [Core:Graphics: WebRender]-Crash in nsObserverService::AddObserver [Win][]
  4. #1435015 [Core:Layout]-Crash when slot used in MathML [@ 0x00000000][@ nsCSSFrameConstructor::ConstructFramesFromItem] [Uns][]
  5. #1435372 [Core:SVG]-MilestoneEntry pass constructor argument by const reference [Uns][]
  6. #1435274 [Toolkit:Form Autofill]-[Forms Autofill V2] - Masked Credit Card is autofilled when master password is activated [All][[form autofill:V2]]
  7. #1431189 [Toolkit:WebExtensions: Frontend]-Add Google Chrome toolbar button color properties [Uns][]

    Partial Landings/Diagnostic Patches:
  1. #1434429 [Core:JavaScript Engine]-More rounds of TokenStream adjustments for UTF-8 tokenizing/parsing [All][]

    Beta 6 -> Beta 7 Changelog +3
  1. #1434580
  2. #1422234 [Core:Editor]-Press enter after an anchor link cause the content in new line associate with the link [Uns][]
  3. #1389759 [Core:Graphics: Layers]-Crash in mozilla::ipc::MessageChannel::CommonThreadOpenInit [Win][[gfx-noted]]

Nightly 60 fixes since 20180122 (Gecko 59) ~517
Beta 59 fixes since 20171113 (Gecko 58) ~2460

Nightly Blog
Release Calendar
Release Tracking
MozRegression Guide
Last edited by Josa on February 4th, 2018, 10:16 am, edited 1 time in total.

Lurtz
 
Posts: 352
Joined: June 12th, 2016, 12:25 pm

Post Posted February 3rd, 2018, 11:57 am

WebRender Project Status Update - Friday February 2nd
https://groups.google.com/forum/#!topic ... 16NeNdjg3U

Defined WebRender Version 1:
Targeting Nvidia discrete graphics cards on desktop computers and Windows 10 (About 4% of the Firefox release user population)

Rollout Plan & Forecast:
Version 1 forecast to be turned on in week 3 or 4 of the 63 Nightly cycle. We will run a two week experiment to see how things perform and gather measurements against our release criteria. Those results will influence our next steps but the current plan is to hold in Nightly and let the V1 feature bake. Based on experiment data from Nightly, the goal is to ride to beta as of 64.

Known Risk(s):
Missed delivery of a dependent milestone
Inability to meet P1 bug burndown required to turn on in Fx 63
2 week experiment in Nightly does not show anticipated performance improvements

Development Status - GREEN

Team is focused on meeting the established release criteria.

Upcoming Milestones:
Enable the last remaining automated tests (expected Fx 61)
Blobs (Expected Fx 61)
Text/Font related work (Expected Fx 62)
Writing various tools to debug and/or develop (Expected Fx 62)
Burn down remaining P1 bugs and Pref ON V1 to 20% (TBD) of the Nightly audience (Expected Fx 63)

Are You A Wiiizard?
 
Posts: 323
Joined: August 30th, 2012, 4:27 am

Post Posted February 3rd, 2018, 4:46 pm

Lurtz wrote:Text/Font related work (Expected Fx 62)


Yikes... looks like I won't even be able to test WR until v62.

Omega X

User avatar
 
Posts: 8099
Joined: October 18th, 2007, 2:38 pm
Location: A Parallel Dimension...

Post Posted February 3rd, 2018, 6:45 pm

They gave themselves a lot of buffer time. I wonder if some of the developers are going on vacation.
Latest: Firefox/63.0.1 *ESR/60.3.0 - Mobile/62.0.3 - Thunderbird/60.3.0
Nightly: Nightly/65.0a1 - Mobile/65.0a1 - Daily/65.0a1

ashleylai87
 
Posts: 166
Joined: December 13th, 2013, 7:40 pm

Post Posted February 3rd, 2018, 7:23 pm

.......Why nvidia?

Almost all corporate and majority of general users have Intel based iGPU.

EDIT: Even mozilla telemety data also shows Intel iGPU being as dominant https://hardware.metrics.mozilla.com/

mayankleoboy1
 
Posts: 446
Joined: February 25th, 2013, 9:52 pm

Post Posted February 3rd, 2018, 8:14 pm

ashleylai87 wrote:.......Why nvidia?

Almost all corporate and majority of general users have Intel based iGPU.

EDIT: Even mozilla telemety data also shows Intel iGPU being as dominant https://hardware.metrics.mozilla.com/


most probably because nvidia has the most stable drivers.
Intel drivers are full of bugs. If you follow the gfx bugs, almost all the driver crashes are with intel drivers. And those are on windows and linux.
Intel drivers are known to be not spec compliant for DirectX and OpenGL.

AMD drivers for older cards are also not very good.

Lurtz
 
Posts: 352
Joined: June 12th, 2016, 12:25 pm

Post Posted February 4th, 2018, 3:45 am

Omega X wrote:They gave themselves a lot of buffer time. I wonder if some of the developers are going on vacation.

If you look at all the open tickets in Bugzilla I don't think it's that much buffer time? There are already meta tickets for things to fix after the first release.

ashleylai87 wrote:.......Why nvidia?

Almost all corporate and majority of general users have Intel based iGPU.

EDIT: Even mozilla telemety data also shows Intel iGPU being as dominant https://hardware.metrics.mozilla.com/

I don't think this is about most users, I think this is about stability and performance.

Omega X

User avatar
 
Posts: 8099
Joined: October 18th, 2007, 2:38 pm
Location: A Parallel Dimension...

Post Posted February 4th, 2018, 5:06 am

Nvidia has the smallest Firefox userbase. They are probably starting with the smallest impact.
Also, I heard that their driver team is difficult at times. So why not get the pain out of the way first.

Lurtz wrote:If you look at all the open tickets in Bugzilla I don't think it's that much buffer time? There are already meta tickets for things to fix after the first release.


Fx64 launches in November, The train moves in August. That's a significant leeway. Also, post release fixes are common for a new graphics system. Firefox has gone through two transplants so far.
Latest: Firefox/63.0.1 *ESR/60.3.0 - Mobile/62.0.3 - Thunderbird/60.3.0
Nightly: Nightly/65.0a1 - Mobile/65.0a1 - Daily/65.0a1

Edds

User avatar
 
Posts: 327
Joined: July 21st, 2010, 1:13 pm
Location: SVK

Post Posted February 4th, 2018, 8:10 am

I think I'm switching to the beta channel until August in this case. Nothing interesting is happening these days for Nightly channel, and don't see something significant on the horizon either.
Core i7 8700K @ 4.8 Ghz + Noctua NH-D15 | 16GB DDR4 3200Mhz Corsair | MSI Z370 GAMING PRO CARBON | MSI GTX 1080 GAMING X @ 2.1/11.0Ghz
Toshiba DT 2TB | Samsung 850 EVO 500GB | Super Flower 650W GOLD 90+ | W10 x64 Pro v1709 | Fractal Define R4 Black | DELL U2515H 1440p
Phone: LG G4 Android 6.0

Lurtz
 
Posts: 352
Joined: June 12th, 2016, 12:25 pm

Post Posted February 4th, 2018, 9:22 am

Edds wrote:I think I'm switching to the beta channel until August in this case. Nothing interesting is happening these days for Nightly channel, and don't see something significant on the horizon either.

Is it too unstable for your everyday use?

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

Post Posted February 4th, 2018, 10:16 am


Return to Firefox Builds


Who is online

Users browsing this forum: No registered users and 3 guests