On October 22, 2026, we held our sixth public meeting with the MySQL community. The theme, “Continued Development Momentum,” captured the progress well: more capabilities in Community Edition, community contributions reaching users, and clearer paths for getting involved.
Our priorities remain delivering innovation into Community Edition, growing the ecosystem, and making MySQL development more transparent and collaborative. This meeting offered plenty of examples of those priorities in action.
More possibilities with Community Edition
There’s a growing list of capabilities for developers to explore. JSON Duality View writes combine document access with relational tables, while field-level JSON updates and ETAG controls provide more control over application behavior. Direct REST endpoints in MySQL Server 26.10 open another way to build applications around MySQL data.
Query processing received attention, too, with the Hypergraph Optimizer and profile-guided optimization in Community 9.7 LTS.
For DBAs and operators, better visibility means more evidence when troubleshooting. Replication applier metrics, Group Replication flow-control statistics, and Health Monitor help answer questions about replication lag, throttling, and resource pressure.
The supporting tools are advancing as well. Highlights included TLS certificate reloading without a restart in Router 26.10, SQL notebooks and an updated Visual Explain in Workbench 26, and upgrade compatibility checks through MySQL Shell.
Security capabilities reaching more users
The security update highlighted post-quantum-capable TLS key exchange in MySQL 26.7 and WebAuthn support in Community 26.10, including FIDO devices for multifactor authentication and passwordless access.
For LTS users, we shared plans to backport post-quantum cryptography capabilities to MySQL 9.7 LTS and 8.4 in January 2027. That timing remains subject to change.
An active roadmap—and a more open development process
Work underway includes native vector indexes using ScaNN, binary log optimizations for large transactions, user-defined types, TidesDB and DuckDB storage engines, and plenty of bug fixes.
Proposals under discussion cover additional vector and AI capabilities, remote plugin installation, Group Replication improvements, pluggable table functions, and binary log and redo log performance. These remain proposals or work in progress, with delivery details still to be determined.
Just as exciting is the direction of the development process itself. Moving more continuous integration and development activity to GitHub supports our longer-term goal of making the mysql-server GitHub repository the true upstream.
There’s also work to do on communication, including more consistent use of GitHub features and clearer status updates for proposals.
Better visibility into bug-fix decisions
Bug backporting prompted an important discussion about what users can expect across LTS releases.
Security fixes are ported to all actively supported versions, and fixes are forward-ported so upgrades do not reintroduce corrected bugs. Other backport decisions involve additional considerations. In the sample presented, more than half of fixes had been ported to all LTS releases.
The feedback was clear: when a fix is not backported to an earlier release, explain that in the bug comments, add context where possible, and revisit decisions when community members raise concerns. Better explanations help users make better upgrade and maintenance decisions.
Contributions that make a difference
One standout example came from Percona contributors Sveta Smirnova and Kamil Holubicki. Following discussion at the May Contributor Summit, their dump-chunking improvement reached MySQL 26.7, delivering more evenly distributed dump chunks for tables with composite primary keys.
The participation numbers were encouraging, too. MySQL 26.7 recorded 43 community contributions from 18 unique contributors, including nine newcomers. The October 16 snapshot for 26.10 recorded another 28 contributions from 18 contributors, including five newcomers.
Behind those numbers are people improving MySQL for everyone—and there’s room for more.
Governance roles, including a Technical Steering Committee and a Vulnerability Group, help clarify oversight and participation. The contribution process connects bug reports, GitHub Discussions, design specifications, pull requests, and project tracking. Code contributions require the Oracle Contributor Agreement.
For anyone taking that first step, Henrik Ingo and I are available to answer questions and help navigate the contribution process.
More ways to be part of the community
Code is only one way to contribute. Planet MySQL’s Ecosystem Showcase now features more than 155 projects, and submissions are welcome. The Community Spotlight and Contributor Profiles series also invites people to share their MySQL experiences, whether through development, teaching, or everyday use.
Heather VanCura’s outreach across Brazil, Portugal, and other parts of Europe brought more opportunities to listen, exchange ideas, and strengthen local community connections.
We’re excited to keep that momentum going. Try a new capability, share feedback from your workloads, report a bug, review a proposal, or tell us about something you’re building. Visit the MySQL Community site, Contributor Guide, or Community GitHub wiki to get involved.
