List view
2FA · multi-user · longer-term feature track
No due date•0/2 issues closedNext hotfix release. Includes community PRs landing post-v0.10.6.1: #297 (Google Meet admission-denial fix) + #320 (Zoom BYO OBF/ZAK token plumbing) — both by Writer/@vikas-writer. Full scope groomed at release-cycle entry.
No due date•0/2 issues closed**Theme: ROBUSTNESS, not features.** Zero new features. The next layer of "in-process state loss + silent classification holes + chart deployability + observability" gaps surfaced after v0.10.4 went into platform staging. **15 packs across 6 domains:** - Chart deployability (Packs A, B, I) — Helm operators on tainted multi-pool clusters can deploy + upgrade safely - Bot lifecycle correctness (Packs D, J, N) — meetings get classified correctly; orphan pods are reaped; bot↔server contracts are checked at PR time - Recording durability (Pack E) — recordings survive pod restarts and Zoom abrupt-stops - Redis client robustness (Pack C) — no silent socket hangs; declarative readiness gating - Browser-session reliability (Pack K) — Redis state index reconciles with K8s ground truth - Operational observability (Packs F, G, H, L, M, O) — production-shape smoke matrix, structured bot logs, dedicated terminal states for transient infra failures, slim list endpoints, row-size monitoring **Principles applied across the cycle:** - No workarounds anywhere - No fallbacks for internal subsystems (allowed only for external non-deterministic systems: Zoom/Meet/Teams DOM) - Single canonical durable mechanism per state transition - Auto-recovery requires mandatory observability (every sweep ships an alert) - Compliance-by-construction (e.g. bot logs lifetime-coupled to meeting retention) - Migration-free: zero PG schema migrations, zero new columns, zero new enum types **Cycle target: T+12 / T+17 no-later-than from groom approval (2026-04-27).** ~15 dev-days, parallelizable. **Retires 4 platform-side workarounds** as OSS lands: cronjob-collector-watchdog (Pack C), cronjob-recording-reconciler (Pack E.1), kubectl-delete-job Makefile preflight (Pack A.2 / #247), planned-then-withdrawn 5-min stuck-stopping cronjob (Pack E.3). **Tracking artifacts:** \`tests3/releases/260427-k8s-stabilize/scope.yaml\` + \`plan-approval.yaml\` + \`groom.md\` in the OSS repo.
No due date•20/31 issues closedNext release. Bundles 7 epics: BotConfig split (#246), Audio-capture (#251), Teams reliability (#252), Zoom SDK recovery (#253), Lifecycle refinement (#255), Segment reconciliation (#256), Self-hosted operator hardening (#257), Meeting video recording (#262). Each epic carries its scope and children; epic-level visibility via the `epic` label. Zoom Web (#254) shipped in v0.10.4 and is no longer scoped to 0.11; remaining Zoom-Web work (full incoming-video decoder shutdown, platform enum split, retire ZOOM_WEB/ZOOM_SDK env-vars, tier-meeting test, Zoom-specific DoDs) lives under #253 / Wave 2 / Wave 3.
No due date•2/60 issues closedActive hardening line for the 0.10 series. Most recently shipped: **v0.10.4** (cycle 260426-zoom, 2026-04-27) — Zoom Web Client as default join path, 4× per-bot CPU reduction via Chromium `--in-process-gpu`, chat persistence race fix, awaiting-admission false-positive fix on Zoom waiting room. See [Release v0.10.4](https://github.com/Vexa-ai/vexa/releases/tag/v0.10.4). Prior cycles: 260424 (blue-stage shakedown), 260422 (release plumbing). Issues in this milestone are blue-stage / community-found defects scheduled to ship in 0.10.x point releases as they're fixed. Larger structural work goes to the [0.11 milestone](../milestone/13).
No due date•0/9 issues closed