66 lines
7.2 KiB
Markdown
66 lines
7.2 KiB
Markdown
**# Major Developments**
|
||
- The planned production release for the Firebase‑to‑AWS migration (Boukili) scheduled for Monday was cancelled; no new release date will be set until blockers are clarified and reliable estimates obtained. (Source: *20 Work/Projects/2026/Boukili/2026-09-10 - Boukili.md*)
|
||
- A “freeze” of code will occur once the currently identified issues are fixed and validated; phase‑2 work will be kept on a separate branch and not merged into phase‑1 during validation. (Source: *20 Work/Meetings/TFO/Produits Numériques (Transversal)/2026-09-11 - Produit Numérique.md*)
|
||
- The OTT delivery is at risk of missing the live‑event deadline (Sept 14) due to regressions; a weekend release may be required to meet the Sept 17 live broadcast. (Source: *20 Work/Meetings/Team Meetings/2026/2026-09-10 - Reunion equipe.md*)
|
||
|
||
**# Risks / Blockers**
|
||
- Potential loss or non‑synchronisation of user data for multi‑device users during the Firebase‑to‑AWS migration; risk heightened if devices remain on different back‑ends. (Source: *Boukili.md*)
|
||
- Ongoing Salesforce regression investigation with no resolution at time of meeting; impacts data migration reliability. (Source: *Boukili.md*)
|
||
- Uncertainty about the reliability of the data migration itself; current suggested solutions (accepting data loss or reduced reliability) are not acceptable. (Source: *Boukili.md*)
|
||
- Insufficient testing time to guarantee a solid version before submission; migration works on test/staging but fails on UAT. (Source: *Produit Numérique.md*)
|
||
- “Last activity” field reliability issues, especially under network failure conditions. (Source: *Produit Numérique.md*)
|
||
- Undefined strategy for forced migration of multi‑device users; critical for submission. (Source: *Produit Numérique.md*)
|
||
- QA capacity bottleneck: only one QA resource covering four sites; risk of delayed testing. (Source: *Reunion equipe.md*)
|
||
- JW Player billing ambiguity: unclear whether fees apply to active address or actual stream usage. (Source: *Direct ONFR - Réponse sur le feed de JWP.md*)
|
||
|
||
**# Decisions Made**
|
||
- Cancelled Monday production release for Boukili migration; defer new date pending clarification. (Source: *Boukili.md*)
|
||
- Code freeze to be applied after fixing and validating identified issues; phase‑2 work isolated on separate branch. (Source: *Produit Numérique.md*)
|
||
- Use the second Corus feed for a test send to JW Player; keep existing feed unchanged; retain both ingest points and request JW Player to delete those that cannot be removed directly. (Source: *Direct ONFR - Réponse sur le feed de JWP.md*)
|
||
- Documentation departmental will be presented under “platform” section; data governance treated as continuous practice; project renamed “projet Données FMC”. (Source: *Reunion equipe.md*)
|
||
- For Idéllo ZIP files, each course/ZIP must have its own Jira ticket; processing will not start before 12 Oct. (Source: *Reunion equipe.md*)
|
||
|
||
**# Decisions Needed**
|
||
- Confirmation of the migration‑forced strategy for multi‑device users and associated user communication plan. (Source: *Produit Numérique.md*)
|
||
- Final delivery date and freeze trigger confirmation for the upcoming release (window 18 Sept – 23 Sept). (Source: *Produit Numérique.md*)
|
||
- Clarification of JW Player billing conditions (address active vs. stream usage). (Source: *Direct ONFR - Réponse sur le feed de JWP.md*)
|
||
- Approval of additional QA resources or temporary reinforcement to address capacity bottleneck. (Source: *Reunion equipe.md*)
|
||
|
||
**# Project Changes**
|
||
- Production schedule for Boukili migration postponed; new schedule pending resolution of data‑migration blockers. (Source: *Boukili.md*)
|
||
- OTT delivery timeline now uncertain; may require weekend release to meet live event on 17 Sept. (Source: *Reunion equipe.md*)
|
||
- Phase‑2 development work will be isolated on a separate branch, not merged into phase‑1 during validation. (Source: *Produit Numérique.md*)
|
||
|
||
**# Vendor Issues**
|
||
- JW Player billing details remain contradictory; need clarification from vendor. (Source: *Direct ONFR - Réponse sur le feed de JWP.md*)
|
||
- Coordination with Corus (contact Chris Sandinot) required to modify second stream address for test. (Source: *Direct ONFR - Réponse sur le feed de JWP.md*)
|
||
|
||
**# Team / Coaching / Recognition**
|
||
- No explicit coaching or recognition items identified in the notes.
|
||
|
||
**# Next‑Week Commitments**
|
||
- Technical point with Abiba to clarify data‑migration issues (deadline: tomorrow morning). (Source: *Boukili.md*)
|
||
- Prepare and circulate email detailing critical blockers for team validation. (Source: *Boukili.md*)
|
||
- Evaluate feasibility, cost, and timeline of IBO intervention on migration with The Mind (starting after tomorrow’s point). (Source: *Boukili.md*)
|
||
- Inform Mohamed of the release postponement after clarification with Abiba. (Source: *Boukili.md*)
|
||
- Obtain duration estimates for resolving remaining problems (responsible: The Mind). (Source: *Boukili.md*)
|
||
- Investigate UAT migration issue and deliver a stable version after a new test cycle (development team). (Source: *Produit Numérique.md*)
|
||
- Implement retry mechanism for “last activity” field and set up visibility indicator for tests (development team). (Source: *Produit Numérique.md*)
|
||
- Exchange with Habiba to define robust solution for validating last activity (responsible: relevant teams). (Source: *Produit Numérique.md*)
|
||
- Study with current agency the possibility of forcing all users to update via Contentful message (Amadou & team). (Source: *Produit Numérique.md*)
|
||
- Verify Salesforce test progress with Nicolas and Mark; communicate update (responsible: relevant team). (Source: *Produit Numérique.md*)
|
||
- Confirm realistic delivery dates by email (development team, due afternoon). (Source: *Produit Numérique.md*)
|
||
- Prepare project presentation for meeting with Francis (due Tuesday 15 Sept). (Source: *Reunion equipe.md*)
|
||
- Continue Umami tracker implementation (Jean‑Claude). (Source: *Reunion equipe.md*)
|
||
- Analyze Mogador sync flows and set up failure alerts (Mohamed Slimane). (Source: *Reunion equipe.md*)
|
||
- Create Jira tickets for each Idéllo ZIP file/course starting 12 Oct (Jason & requestors). (Source: *Reunion equipe.md*)
|
||
- Perform targeted regression tests on TFO live/carousel delivery before 16‑17 Sept (Ajar). (Source: *Reunion equipe.md*)
|
||
- Conduct exchange on service‑tracking recommendations for MAMI (Rabiba & Amandou). (Source: *Reunion equipe.md*)
|
||
- Test second Corus feed to JW Player and report results (responsible not specified). (Source: *Direct ONFR - Réponse sur le feed de JWP.md*)
|
||
|
||
**# Sources**
|
||
- 20 Work/Projects/2026/Boukili/2026-09-10 - Boukili.md — production release cancellation, blockers, actions.
|
||
- 20 Work/Meetings/TFO/Produits Numériques (Transversal)/2026-09-11 - Produit Numérique.md — code freeze, delivery window, risks.
|
||
- 20 Work/Meetings/Team Meetings/2026/2026-09-10 - Reunion equipe.md — OTT delivery risk, Boukili migration complexity, QA capacity, project naming, Idéllo ZIP process.
|
||
- 20 Work/Projects/2026/OTT/2026-09-10 - Direct ONFR - Réponse sur le feed de JWP.md — JW Player feed test, billing ambiguity.
|