442
edits
(→Risks/Issues: added new issue) |
(links) |
||
| Line 5: | Line 5: | ||
=== Overall Project Health === | === Overall Project Health === | ||
Green - r41 is go live for unified Telemetry. All issues triaged and assigned milestones. Dev Team continues to focus on data validation. | Green - r41 is go live for unified Telemetry. All issues triaged and assigned milestones. Dev Team continues to focus on data validation, client side pings being the current focus. | ||
=== Exec Summary === | === Exec Summary === | ||
| Line 18: | Line 18: | ||
! Description of Risks/Issues !! State !! Owner !! Plan to Resolve/Mitigation !! Target Date | ! Description of Risks/Issues !! State !! Owner !! Plan to Resolve/Mitigation !! Target Date | ||
|- | |- | ||
| Investigate gaps in pings || Open || Stuart/Alessio || https://bugzilla.mozilla.org/show_bug.cgi?id=1185123 || 8/04 | | Investigate gaps in pings || Open || Stuart/Alessio || https://bugzilla.mozilla.org/show_bug.cgi?id=1185123 [https://etherpad.mozilla.org/u230yVoP9S working doc] || 8/04 | ||
|- | |- | ||
| Data integrity between V2/V4 and V4 internal data consistency || Open || Brendan/Sam || Investigation in progress. Added resources (Sam). https://etherpad.mozilla.org/fhr-v4-validation || 7/30 | | Data integrity between V2/V4 and V4 internal data consistency || Open || Brendan/Sam || Investigation in progress. Added resources (Sam). https://etherpad.mozilla.org/fhr-v4-validation || 7/30 | ||
edits