Skip to content

Roadmap to 1.0

dlagoCalimaco edited this page Jul 24, 2026 · 11 revisions

Roadmap to 1.0

LakeDB 0.11 beta capabilities, upcoming 1.0 trust milestone and future ideas

LakeDB grows through clear product milestones. This roadmap records the evolution from 0.1 to today's 0.11 public beta and defines the remaining trust work before a stable 1.0.

The milestones tell the product story and do not all map one-to-one to archived downloadable binaries. The latest release is the supported download.

Product evolution

Version Theme Product milestone
0.1 Foundation The first focused local MySQL and MariaDB desktop foundation.
0.2 Connections Multiple connections, folders, environments, SSL/SSH and independent workspaces.
0.3 SQL workspace SQL editing, tabs, object exploration, history, favorites and result navigation.
0.4 Safe data Table editing, read-only mode, production safeguards, filtering, paging and data exchange.
0.5 Database tools Diagnostics, configuration backup, backup/restore, schema comparison and table copy.
0.6 Cross-platform macOS, Windows and Linux packages, English/Spanish UI, international documentation and community.
0.7 beta Resilience Update notices, safe restores, tab/crash recovery, migration snapshots, credential binding and accessibility checks.
0.8 beta Safe editing polish Visible pending-row states, positional duplication, structured large-value editing and validation feedback.
0.9 beta Migration, workspace clarity and large exports Migration Studio, safer backup/restore, clearer active-connection workspaces and configurable streaming exports up to 50 million rows.
0.10 beta Smarter daily workflow Split query/table panes, schema-aware completion, alias and index guidance, flexible formatting, typed cell editors, review-first connection imports and clearer Home navigation.
0.11 beta — current Operational public beta Explain plans, visual transactions, Quick Open, persistent snippets, SQL-first object editing, granular schema comparison, session monitoring and in-app feedback.

Before 1.0

Signed distribution

Obtain Apple and Windows signing identities, integrate them into the official local publisher, notarize macOS packages and verify signed installation on clean systems. Stable tags are intentionally blocked until this path exists.

Smooth updates — in beta

Update discovery, preserved workspace state and guarded local-data migrations are now in beta validation. Before 1.0, upgrades from the retained 0.9 and 0.10 lines must be exercised with real profiles, credentials, sessions and recovery snapshots.

Polish and accessibility

Keyboard navigation, focus and screen-reader improvements now include automated serious/critical checks for the shell. Critical dialogs, tables and database workflows still need a complete keyboard and assistive-technology review. Onboarding, performance budgets and visual consistency remain release gates.

Stability and compatibility

A documented, tested operating-system and MySQL/MariaDB compatibility matrix; packaged smoke tests on Windows and Linux as well as macOS; and a release-candidate soak with no open data-loss, credential, restore, update or destructive-query blockers.

Public release readiness

Publish clear licence and privacy terms, supported-version expectations, security-reporting guidance and known limitations. Freeze the 1.0 scope during the release-candidate period so testing is not invalidated by new workflow changes.

LakeDB 1.0

Version 1.0 is the stable LakeDB foundation: dependable, documented and upgrade-safe for daily MySQL and MariaDB work across supported platforms.

The roadmap is a direction, not a fixed schedule. Scope can change with product learning and community feedback.

Help define 1.0

Use Ideas to propose workflows and vote. Bugs and data-safety issues can change priority even when another idea has more votes.

See Version History for the smaller changes in each build.

Clone this wiki locally