Roadmap

QoreDB's roadmap is public. You can see what's planned, what's in progress, and what's been shipped, plus contribute ideas of your own.

Where to read it

Browse the live roadmap on the QoreDB site at qoredb.com/roadmap. It's updated as priorities shift; what's "next" today may move depending on user feedback and bug reports.

The roadmap groups items into a few buckets:

• Shipped: features that have landed in a release. Cross-referenced with the changelog.
• In progress: actively being worked on. These usually ship in the next minor release.
• Next up: queued, but not started yet. Order is the rough priority.
• Considering: ideas under evaluation. Feedback here has the most leverage; the decision to schedule them depends partly on user demand.

Suggesting a feature

Two ways to influence the roadmap:

• Open a GitHub issue at github.com/QoreDB/QoreDB/issues with a clear use case. Describe what you're trying to do, not just what you want changed; that helps frame the discussion around the actual problem.
• Join the Discord to discuss ideas before they become issues. Sometimes the right design comes from a conversation rather than a one-off ticket.

The clearer the use case, the better the chance the request lands on the roadmap.

Reporting a bug

Bug reports go to the same GitHub issue tracker. Include:

• Your operating system and QoreDB version (Help → About).
• The driver and engine version, if it's database-specific.
• Steps to reproduce, ideally minimal.
• What you expected vs. what happened.

Logs from the Error Logs panel (in the sidebar footer) often help; attach them when they're relevant.

What's not on the roadmap

The roadmap is the source of truth for committed work. If something isn't on it, it isn't planned. Open an issue or join the Discord to advocate for it.

Where to go next

• Changelog for what shipped and when
• Contributing if you want to ship a feature yourself
• License for what you can do with the codebase