3 Month Roadmap: Dec, Jan, Feb

1. Maintain a Healthy and Manageable Backlog of Open PRs and Issues

Goal: Ensure any one developer can maintain a clear overview of all open PRs and issues.

Right now, it’s difficult to identify what needs attention and when, due to the sheer volume of open issues and PRs. To address this, we’re focusing on reducing the backlog by clearly defining scope, leveraging automation, and establishing a well-defined intake process.

Clearly Define the Scope of the ORM Project

Prisma supports a wide variety of systems and conditions. In the manifesto, we outlined a list of first-class databases. Building on this, we’ll publish a clear list of first-class environments, frameworks, integrations, and versions we’ll officially support.

• Publish the first-class databases list
• Publish the first-class operating contexts list

Reduce Open Issues and PRs

Using tools like Dosu and a bit of elbow grease, we’ll refine our backlog by closing stale or duplicate issues and prioritizing those aligned with first-class databases and operating contexts. For items outside our focus, we’ll encourage community contributions.

• Significantly reduce the volume of open issues and PRs, ensuring only actionable and relevant items remain

Establish Metrics for Bug Report Management

We’ll track Time to Repro (how quickly we confirm a bug) and Lead Time (how quickly it’s fixed) to keep the backlog manageable and responsive. Our target is to confirm bugs within 14 days and resolve them within 1 month.

• Time to Repro for recent bugs is ≤14 days
• Lead Time for recent bugs ≤1 month

2. Reconnect with the Community

We’re committed to showing that we take your feedback seriously. Beyond managing the backlog, we’ll focus on delivering high-value updates and setting clear timelines for the preview features you depend on.

Resolve Highly Upvoted GitHub Issues

We’ll resolve and close several of the most upvoted issues (bugs or features) that the community has highlighted as priorities. We expect to finalize which issues to focus on by December 13th and will update this post with references to those issues.

• Resolve 5 highly upvoted GitHub issues:
  • Add multi-line / block comments to PSL / schema.prisma file #4474 (👍🏻 62)
  • Support for Json field type in SQLite #3786 (👍🏻 199)
  • Implement RETURNING on updateMany() so it can return data (instead of just count) #5019 (👍🏻 160)
  • Support ULID #13679 (👍🏻 91)
  • Support enum in SQLite (via polyfill) #2219 (👍🏻 203)

Publish Timelines for Preview Features

By the end of the February, every preview feature will have a clear public timeline for when it will move to GA—or, if necessary, what its future holds.

• 100% of preview features have a public timeline

Deliver Two Preview Features to GA

We’ll focus on completing and shipping the following features:

• Deliver the tracing feature to GA
• Deliver the omitApi feature to GA

Host Regular AMAs

We’ll host three AMAs to engage with the community and provide updates on progress. The December AMA will focus on the manifesto and address your questions about it. For the January and February AMAs, we’d love to hear your suggestions for topics you’d like us to cover.

• December AMA (focused on the manifesto)
• January AMA (topic: Migrating from Rust to TypeScript)
• February AMA (topic: Driver Adapters)

3. Query Execution Moves to TypeScript

We’re making significant progress toward migrating from Rust to TypeScript. Over the next three months, we’ll focus on the query compiler project. This will enable queries built by the Prisma Client to be converted into an intermediate structure previously executed by the Rust core and move the execution to TypeScript. If that sounds arcane, here’s the takeaway: more of the core logic will move to the TypeScript layer, eliminating the dependency on the native binaries, reducing back-and-forth between layers and making the codebase more accessible for TypeScript contributors in the future.

Release Query Compiler into Early Access

By the end of the February, we’ll deliver an early access feature implementing a limited subset of the Prisma API using the new architecture. This will help validate our approach and guide collaboration with third-party client maintainers.

• Deliver the Query Compiler to early access

Merge Driver Adapters into the Query Compiler Project

The Driver Adapters preview feature will become part of the Query Compiler project. Going forward, driver adapters will be the sole method for database communication in Prisma.

• Discontinue the driver adapters preview feature