Services/Sync/Meetings/2010-10-20: Difference between revisions
Jump to navigation
Jump to search
(6 intermediate revisions by 3 users not shown) | |||
Line 4: | Line 4: | ||
=== Ops === | === Ops === | ||
==== EC2 ==== | |||
* LDAP/web/db running but ran into issues trying to get application working. | |||
* openvpn instances crash a few days later due to conflicts with ec2 | |||
* legal review still pending | |||
==== Delete account fix ==== | |||
* reg-server 1.3.101020 push to stage w/qa, then production | |||
=== J-PAKE === | |||
* [[Services/Sync/SyncKey/J-PAKE/Timeline|Draft timeline]] up, some fuzziness to fill in after discussion. Work is continuing on all fronts. | |||
=== Fx Sync === | === Fx Sync === | ||
* [[Services/Sync/SyncKey/J-PAKE|J-PAKE]] | * [[Services/Sync/SyncKey/J-PAKE|J-PAKE]] backend pending review. | ||
* [[Services/Sync/SimplifyCrypto|Crypto simplification]] project kicked off (better perf, less network I/O) | * [[Services/Sync/SimplifyCrypto|Crypto simplification]] project kicked off (better perf, less network I/O) | ||
Line 13: | Line 27: | ||
* 1.0.4 builds being tested by QA | * 1.0.4 builds being tested by QA | ||
* J-PAKE | * J-PAKE framework in place, UI yet to come. | ||
=== Server === | === Server === | ||
* [[Services/Server/Deployments/Sync/1.5|1.5 deployment]] | * [[Services/Server/Deployments/Sync/1.5|1.5 deployment]] targeted for ~2 weeks from now | ||
** All bugs are filed and chained from {{bug|604131}} | ** All bugs are filed and chained from {{bug|604131}} | ||
** Toby has the lead from the Engineering side | ** Toby has the lead from the Engineering side | ||
Line 26: | Line 40: | ||
== Roundtable == | == Roundtable == | ||
* New user activations - do we have an estimate based on load tests? | |||
* Perf status, targets, benchmark | |||
* EC2 status? | |||
* Client/Server functional spec for other clients | |||
* Timeline and coordination for: | |||
** J-PAKE | |||
** Crypto backend change | |||
* New Sync engineering meeting time? | |||
== Notes and actions == | == Notes and actions == | ||
* Need to plan out and coordinate roll-out for the crypto simplification project. | |||
* By Oct 27, we will have a number for new user activation rate. | |||
* MConnor owns documenting the client functional spec, there appears to be a disconnect as to whether this is considered a blocker for FxHome improvements. Need to follow up offline. | |||
=== Fx 4 client === | === Fx 4 client === |
Latest revision as of 16:59, 20 October 2010
- Time: Wednesday at 9:15AM PDT / 12:15PM EDT / 4:15 UTC.
- Place: Mozilla HQ, 3V (Very Good, Very Mighty)
- Phone (US/Intl): 650 903 0800 x92 Conf: 8616#
- Phone (Toronto): 416 848 3114 x92 Conf: 8616#
- Phone (US): 800 707 2533 (pin 369) Conf: 8616#
Technical
Ops
EC2
- LDAP/web/db running but ran into issues trying to get application working.
- openvpn instances crash a few days later due to conflicts with ec2
- legal review still pending
Delete account fix
- reg-server 1.3.101020 push to stage w/qa, then production
J-PAKE
- Draft timeline up, some fuzziness to fill in after discussion. Work is continuing on all fronts.
Fx Sync
- J-PAKE backend pending review.
- Crypto simplification project kicked off (better perf, less network I/O)
Fx Home
- 1.0.4 builds being tested by QA
- J-PAKE framework in place, UI yet to come.
Server
- 1.5 deployment targeted for ~2 weeks from now
- All bugs are filed and chained from bug 604131
- Toby has the lead from the Engineering side
Metrics
Product
Roundtable
- New user activations - do we have an estimate based on load tests?
- Perf status, targets, benchmark
- EC2 status?
- Client/Server functional spec for other clients
- Timeline and coordination for:
- J-PAKE
- Crypto backend change
- New Sync engineering meeting time?
Notes and actions
- Need to plan out and coordinate roll-out for the crypto simplification project.
- By Oct 27, we will have a number for new user activation rate.
- MConnor owns documenting the client functional spec, there appears to be a disconnect as to whether this is considered a blocker for FxHome improvements. Need to follow up offline.