Assuming sequential execution and ~16 weeks total duration starting March 16, 2026, here are the expected completion dates: Change 1 – Design Finalization & Architecture Approval (3 weeks) Expected completion: April 6, 2026 Change 2 – Core Session State Machine Implementation (4 weeks) Includes this bug Bug 2020962 Expected completion: May 4, 2026 Change 3 – Per-Session Sampling & Diagnostics (2 weeks) Includes Bug 2020965 Expected completion: May 18, 2026 Change 4 – Payload Schema & Metadata Integration (2 weeks) Includes Bug 2020963 Expected completion: June 1, 2026 Change 5 – Performance & Payload Impact Validation (2 weeks) Includes Bug 2020967 Expected completion: June 15, 2026 Change 6 – ETL Modeling & Pilot Rollout (3 weeks) Includes Bug 2020968, Bug 2020970 Expected completion: July 6, 2026 Overall projected completion: July 6, 2026 (Flows would follow in a separate, later phase: Bug 2020971)
Bug 2020962 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Assuming sequential execution and ~16 weeks total duration starting March 16, 2026, here are the expected completion dates: Step 1: Design Finalization & Architecture Approval (3 weeks) Expected completion: April 6, 2026 Step 2: SDK/parser/pipeline implementation (estimate 6-8 weeks) - Core Session State Machine Implementation - Per-Session Sampling & Diagnostics - Payload Schema & Metadata Integration Expected completion: May 18, 2026 Step 3: Performance & Payload Impact Validation (2 weeks) Includes Bug 2020967 Expected completion: June 8, 2026 Step 4: ETL Modeling & Pilot Rollout (3 weeks) Includes Bug 2020968, Bug 2020970 Expected completion: June 30, 2026 Overall projected completion: July 6, 2026 (Flows will follow in a separate, later phase: Bug 2020971)