Update the roadmap to reflect 2025/2026 #214
Conversation
| Delivery Quarter: Q2 2025 | ||
| High level objectives (non-exhaustive): | ||
| * SQLite based. | ||
| * Rust interfaces. |
There was a problem hiding this comment.
Don't think there's any specific plan for rust interfaces at the moment, though obviously it'd be usable from rust, and c++ and js.
| * Migrations. | ||
| * Rollbacks. |
There was a problem hiding this comment.
I don't know what "Migrations"/"Rollbacks" mean in this context.
Does this refer to the DB as a whole, or to transactions affecting the database (eg grouping multiple atomic operations)?
Going to assume it means the former: upgrading/downgrading the app, and migrating existing data.
Obviously we need forward migrations from older databases (including mork) to newer ones.
But there's not been any policy discussion on being able to roll back to an older version from a newer version (either legacy new db). Either you need to ship builds which can roll back from a future version (hard! error prone! likely impractical!), or you backport a rollback procedure to an earlier version and make sure users know which versions support which rollbacks.
| * Rust interfaces. | ||
| * Migrations. | ||
| * Rollbacks. | ||
| * Build in parallel and populate it alongside the current database. |
There was a problem hiding this comment.
There is no plan to have both legacy and new databases running in parallel simultaneously. They will both be compiled in, and you can switch between them with a preference, but they won't be running at the same time.
3 participants
No description provided.