diff --git a/TODO_TODAY.md b/TODO_TODAY.md index f3b86668..39b89d64 100644 --- a/TODO_TODAY.md +++ b/TODO_TODAY.md @@ -3,6 +3,50 @@ What is open as of 2026-11-17 (nightly at 2.16.8, stable at 2.3.0). Security items live in `TODO_SECURITY.md`. +## v3 + +Stable has been on 2.3.0 since 2026-11-02, with 273 commits on `nightly` +since. Every Stable user jumps across all of it in one update, so v3 is a +release with a freeze and a test pass, not a plain promote. In order: + +- [ ] **Feature freeze.** Fixes only on `nightly` until v3 ships. +- [ ] **Decide what leaves Labs.** Several connections at once and the tree + sidebar: graduate both to the default (they are what the site and the + email show) and test them as the default on every engine, or ship v3 + with them still opt-in. +- [ ] **Test the jump from 2.3.0.** Install 2.3.0 with real saved connections, + settings, saved queries, a theme and a Pro license, then update to the + v3 build through the updater. Connections, keychain passwords, + settings, query history, notebooks and Pro all have to survive. On + macOS, Windows and Linux: the updater is what breaks first. +- [ ] **AI access levels for built-in models.** The Read only / Read & write + control exists for local agents only (enforced by the MCP server). + Built-in models (Stroke Free, API keys) can run writes, asking only + before destructive ones. Enforce a level in `AiChat`'s `execute_sql` + with the same classifier as `src-tauri/src/mcp/access.rs`, then show + the control. +- [ ] **echarts 6** (PR #14): clears the echarts XSS advisory; the charts need + testing. +- [ ] **Real hardware.** Windows: theme switching and zoom without flicker, + Alt+K in the SQL editor, the title bar with the sidebar on the right, + the new fonts, and a click through every page. macOS: offline Pro (sign + in as Pro, Wi-Fi off, Pro stays on). +- [ ] **Faster startup.** Lazy-load the heavy pages: the entry is 1.3MB and + 143 chunks (1.5MB, the DataTable alone 405KB) preload at startup. New + users on Windows notice this first. +- [ ] **The license change**, settled before the release: the same wording on + the site's legal pages, in the app (license page, About) and in the + email. +- [ ] **Release notes: what changed since 2.3.0.** Written once, used for the + release page, the in-app What's new, the email and the launch posts. +- [ ] **Rollback plan.** Keep the 2.3.0 installers easy to find, and know how + to point the Stable updater back at 2.3.0 if v3 breaks something on day + one. +- [ ] **Release candidate.** A few days of daily use on Nightly with nothing + new landing. +- [ ] **Ship it.** Label the release PR `release:major` (CONTRIBUTING.md), then + Actions, *Promote nightly to stable*. + ## Website The site is `stroke-web` (TanStack Start on Cloudflare Workers). @@ -17,6 +61,8 @@ The site is `stroke-web` (TanStack Start on Cloudflare Workers). - [ ] **A demo on the site.** A short screen recording of real use (connect, browse, query, ask the AI) near the top of the home page, with a poster frame so the page doesn't wait on the video. +- [ ] **Measure it.** Downloads per OS and trial-to-Pro conversion, so the + redesign has numbers to be judged by. ## Email @@ -32,3 +78,22 @@ for purchases and failed payments only; nothing sends to every user yet. - [ ] Both need a broadcast path: a template per email, the recipient list (users, or license holders only), an unsubscribe link, and a test send to myself before the real one. + +## Launch week + +After v3 is on Stable: the website, then the emails, then the posts, the +same week. + +- [ ] **First-run tour in the app.** Everyone the launch brings in lands on + the empty connect page. A sample database (a bundled SQLite file) that + opens in one click, and a short tour of the tree sidebar, the AI chat + and the command palette. +- [ ] **Launch posts.** Product Hunt, Show HN, r/PostgreSQL and r/SQL, the + same day as the email, with the demo recording and the new pictures. + +## After v3 + +- [ ] **Schema diff** between two databases: tables, columns, indexes and + constraints that differ, and the SQL that brings one up to the other. +- [ ] **Query parameters**: `:name` / `$1` in a query asks for values (and + remembers the last ones) before it runs.