Daily stand-up — mobile app team, release 4.2
Release 4.2 stays planned for Thursday if the load test passes by Wednesday noon; the broken load test environment is the main risk.
Summary
Four updates. Offline drafts are finished and waiting for review, the notification settings screen is in progress, rate limiting for the sync API is on staging and the regression tests are 70% done. The load test environment has been down since yesterday, which blocks the last check before Thursday’s release. The team agreed to keep the release date if the load test passes by Wednesday noon.
Participants
- Nina Patel — iOS developer
- Leo Grant — Android developer
- Ama Mensah — backend developer
- Felix Romero — QA, runs the stand-up
Agenda
- Round of updates
- Release 4.2 readiness
Decisions
- Release 4.2 stays on Thursday if the load test passes by Wednesday noon.
Action items
| Owner | Task | Due |
|---|---|---|
| Ama Mensah | Ask the platform team to restore the load test environment | Today |
| Leo Grant | Review Nina’s offline drafts pull request | This morning |
Updates by person
| Person | Done / in progress | Next | Blockers |
|---|---|---|---|
| Nina Patel | Offline drafts finished; pull request open | Fix the date picker crash on iPad | Waiting for review |
| Leo Grant | Notification settings screen in progress | Finish the screen; review Nina’s pull request | - |
| Ama Mensah | Rate limiting for the sync API deployed to staging | Load test before the release | Load test environment down since yesterday |
| Felix Romero | Regression tests for 4.2, about 70% done | Finish the regression tests | - |
Blockers and risks
- The load test environment is down; without the load test, Thursday’s release is at risk.
- Offline drafts can’t be merged until the review is done.
Next meeting
Tomorrow, 9:30.