Confirmed users
631
edits
(→Agenda) |
(→Agenda) |
||
| Line 21: | Line 21: | ||
* [ON TRACK] Security policy updates through new update service ("Balrog 2.0") (Tracking: 1184528) | * [ON TRACK] Security policy updates through new update service ("Balrog 2.0") (Tracking: 1184528) | ||
''Update from Tarek: | |||
Server-side I think we're pretty much done at this point, to cover the needs of the first version of the security settings client. | |||
In terms of timeline I've talked with several folks and I just want to reiterate here the plan: | In terms of timeline I've talked with several folks and I just want to reiterate here the plan: | ||
# The goal is to land in Firefox 44. | |||
# Once Mark is ready to ship v1 in Firefox (sometimes in the next 2/3 weeks) it'll be shipped behind a flag to deactivate it, so the existing OneCRL client still works. It will also have a way to configure the Kinto endpoint in about:config | |||
# We'll deploy a test server then in coordination with Travis' team, and starts to QA the new client with Nightly in coordination with Stuart's team. | |||
# Once everyone is happy, and we're getting good at qa/deploy cycles - with all the standard staging procedures rolling, we'll toggle the flag so all nightlies use the new thing | |||
# If nothing bad happens, we'll let it bubble up in 44 | |||
# We'll iterate on introducing notifications (balrog) / signing on the client side - maybe the notification part will be ready on time for 44. In the interim, the client simply fetches once every 24h. | |||
'' | |||
===Q4 Goals=== | ===Q4 Goals=== | ||
* Implement Hello UI as an add-on [DONE early!!!], and ship it via go-faster. | * Implement Hello UI as an add-on [DONE early!!!], and ship it via go-faster. | ||