(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)

Security is getting ongoing coverage primarily through fuzzing.

(No comment was entered for this change.)

(No comment was entered for this change.)

chatted w/ Gavin

as per discussion w/ Jeff

Since this is a backend improvement, we don't anticipate that new Help Center is needed. Feel free to reach out to us if you feel differently. 

Thanks.

moving to M14, since it's now behind a flag in M13.

(No comment was entered for this change.)

(No comment was entered for this change.)

met with Linus today; tentative green light for launch in M14, but there are reports of blue-screening on some users' machines which needs to be investigated. Any remaining crashes should be fixed too of course.

Only shipping on Windows and Linux in M14. Mac will have to come in a later release.

Running M14 on Linux with the i915 driver yields extremly low performance.
Sysprof indicates software-fallbacks are executed in the opengl driver.

#14: Intel gpus are explicitly blacklisted on linux as the driver quality is spotty.

Moving this from Mstone-14 to Mstone-15, b/c as I understand it, GPU-accelerated Canvas2D has been disabled on M14, but we're trying to ship it in M15.

(No comment was entered for this change.)

My understanding is we are intentionally not making much noise about this yet. Alex K, if you'd like us to mention it in blog posts (e.g. the M15 Stable blog post), let me know.

I don't think there are any accessibility implications here, but let me know if that's not true.

Current status: Accelerated 2D canvas is OFF by default in Chrome 15 and 16, and ON on ToT. Assuming all remaining issues are resolved, it will stay on for Chrome 17.

(No comment was entered for this change.)

gotcha; thanks for updating the bug. Definitely useful for when we prep the scope review for each release.

as per conversation w/ Tom (wiltzius@)

Actually.. according to mal@, "Plan is to keep accelerated canvas on into 17 Beta."

So, moving this back into M17 for QA purposes. But we should move it back to Mstone-18 if and when we disable it on M17 and adjust target to M18.

Moving bugs marked as Available but not blockers from M17 to M18.  Please move back if you think this is a blocker, and add the ReleaseBlock-Stable label.  If you're able.

(No comment was entered for this change.)

Still scheduled to be turned off mid-January.

hey Tom,

Has GPU-accelerated canvas2d been disabled on the M17 branch yet? Or are you going to wait until closer to M17 Stable? (2/7)

Related question: Will you be keeping this enabled or disabled for M18? (M18 Beta will also be in mid-Feb, a bit later than M17 Stable)

We did disable this in 17

Cool. I'm going to go ahead and mark this as Mstone-18 for now then.

We still hope to hit M-18 (stable) for this. We're getting close; there are
several large patches that need to land to fix performance in corner cases
(and ongoing testing that needs to happen, which I'm praying won't turn up
more trouble cases). The thing basically works, we just want to make sure
performance is as good as we think it can be. There's little harm in
leaving it on in beta, but we've set a high bar for stable.

On Saturday, January 21, 2012, wrote:

Reviewed w/ Linus and the TPMs today; we are a Go for M18.

discussed w/ mcginty@ and steng@ (LegalReview-Yes)

we are discussing (potentially) including this in the M18 Beta blog post with wiltzius@ and vangelis@.

(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)