Confirmed users
1,225
edits
Connected Devices/Projects/Metrics/Sprint 1: Difference between revisions
Connected Devices/Projects/Metrics/Sprint 1 (view source)
Revision as of 09:28, 29 March 2016
, 29 March 2016→Tasks or Bugs committed for this sprint
| (15 intermediate revisions by the same user not shown) | |||
| Line 38: | Line 38: | ||
|- | |- | ||
| JSON serialization | | JSON serialization | ||
| | | Tamara | ||
! style="background:#00B2FF;" | Done | ! style="background:#00B2FF;" | Done | ||
| First decision was using rustc-serialize but actually '''serde''' was decided to be used instead. This is where the standard is going, it's supposed to be more efficient and have more features. Additionally, Tamara was able to serialize our complex nested structures with this vs. rustc_serialize. Merged with [https://github.com/tamarahills/metrics_controller/commit/e3f631208f18121fe9a98804e78e2d6b15d3c8f2 issue#2] | | First decision was using rustc-serialize but actually '''serde''' was decided to be used instead. This is where the standard is going, it's supposed to be more efficient and have more features. Additionally, Tamara was able to serialize our complex nested structures with this vs. rustc_serialize. Merged with [https://github.com/tamarahills/metrics_controller/commit/e3f631208f18121fe9a98804e78e2d6b15d3c8f2 issue#2] | ||
| Line 54: | Line 54: | ||
| Send Crash Ping to server and verify that it’s received | | Send Crash Ping to server and verify that it’s received | ||
| Tamara | | Tamara | ||
! | ! style="background:#00B2FF;" | Done | ||
| | | | ||
|- | |- | ||
| Review Firefox telemetry / crash pings to see if we could adapt for use in CD | | Review Firefox telemetry / crash pings to see if we could adapt for use in CD | ||
| Tamara | | Tamara | ||
! | ! style="background:#00B2FF;" | Done | ||
| Created a draft ping: https://docs.google.com/document/d/1Mak6dpmmvAxhnbms34zCELSb_46s0-iaTQuCpkr8i34/edit | | Created a draft ping: https://docs.google.com/document/d/1Mak6dpmmvAxhnbms34zCELSb_46s0-iaTQuCpkr8i34/edit | ||
|- | |- | ||
| Line 69: | Line 69: | ||
| Gzip the payload (for Crash Ping) | | Gzip the payload (for Crash Ping) | ||
| Russ | | Russ | ||
! | ! style="background:#00B2FF;" | Done | ||
| | | Once we had a crash ping payload, we have to use the gzip functionality to gzip compress the crash ping payload. | ||
|- | |- | ||
| Background reading on existing Telemetry and Metrics tools at Mozilla | | Background reading on existing Telemetry and Metrics tools at Mozilla | ||
| Michael | | Michael | ||
! | ! style="background:#00B2FF;" | Done | ||
| | | | ||
|- | |- | ||
| Line 84: | Line 84: | ||
| Complete the CD metrics wiki with Program Status, Projects Deliverables and Milestones | | Complete the CD metrics wiki with Program Status, Projects Deliverables and Milestones | ||
| Maria | | Maria | ||
! | ! style="background:#FF2800;" | Not finished | ||
| | | Not finished, Moved to sprint 2 | ||
|- | |||
| Investigate getting os/platform info from within rust (for Crash Ping) | |||
| Michael | |||
! style="background:#00B2FF;" | Done | |||
| FillZpp module, checked also that it works when used in a java environment calling the public functions from FillZpp. | |||
|- | |||
| Figure out how to handle retries | |||
| Tamara | |||
! style="background:#00B2FF;" | Done | |||
| Merged in controller library [[https://github.com/tamarahills/metrics_controller/commit/aee4c0975d81b992ac0cf6e57b5c8a0997c7bd4f |PR #12]] | |||
|- | |||
| Unit test controller retry logic | |||
| Russ | |||
! style="background:#FF2800;" | Not finished | |||
| Create a mock object to unit test the retry logic. That is, mock sending the data to the server and be able to dictate whether the send succeeds or fails after a certain number of attempts. Not finished, moved to Sprint 2 | |||
|- | |- | ||
|} | |} | ||
| Line 93: | Line 108: | ||
== Demos == | == Demos == | ||
Tamara showed us in the console how she's sending the crash ping to the Telemetry server and how it's been received although we still need to figure out the validation problems. That will be part of the work planned in Sprint 2 | |||
== Retrospective == | == Retrospective == | ||
| Line 99: | Line 115: | ||
=== Things that went well === | === Things that went well === | ||
* | * Team is enthusiastic / works well together, generally good vibe (+1) | ||
* Russ working directly with Michael (1:1 in the office) worked well | |||
* Trello board and tasks breaking down, really helpful to track the progress | |||
* Meetings: standup, it helps the team to be on the task | |||
* The #rust channel was a savior twice I think! | |||
=== Things that went not that well === | === Things that went not that well === | ||
* | * Took more time than I wanted to get the local pipeline running. | ||
* Took more time than I wanted to get the code for the retry mechanism working. | |||
* Dominik’s role, we’ll miss him (+1) | |||
* We should all fill out this retro before this meeting as it’s awkward to do it now :) (you are right!!) | |||
=== Actions for this sprint === | === Actions for this sprint === | ||
* | * ['''AP Maria'''] Check with Peter the date/content for the Metrics presentation in the Product Management meetup (date April 18th to be confirmed) | ||
* ['''AP Maria/Dylan'''] we need to figure out who will be in charge of the Data Store staff, check with Marshal/Bertrand. | |||
* ['''AP Maria'''] send a reminder to fill in the Retrospective on Friday before the Sprint Planning | |||
* Want to talk about duplication of trello board vs. Github issues. | |||
** Github issues are more related to code actions, so it's not necessary adding all of them in the Trello board | |||
* ['''AP Maria/Dylan'''] Need to better understand how we’re plugging the PM gap, to figure out roles there | |||
* ['''AP Maria'''] Transfer Dominik’s weekly meeting googledoc ownership | |||
* ['''AP Dylan'''] Identify tasks that we’ll need help from Mark’s team, see if we can get some of their time allocated in Q2 | |||
* ['''AP team'''] We, as a team, we could align at high level the Q2 objectives of our team. We'll talk about it in the following standup meeting (tomorrow, March 29th) | |||