🎯 📅 EVA Roadmap Planning

We follow a Just-In-Time planning approach, meaning that we plan our work at most 2 months in advance. Even within that window, we tend to re-prioritize based on user feedback. Therefore, any features or items that you see on our roadmap more than one version out are subject to change.

💡 Feature Prioritization:

We prioritize features based on several factors, including the number of people asking for them, features/fixes that are small enough to be addressed while we work on other related features, features/fixes that help improve stability and relevance, and features that address interesting use cases that excite us!

🎯 Requesting a Feature:

If you have a feature request that you would like to prioritize, please add a use-case for it. You can either add your comment to an existing issue (along with a thumbs-up 👍)) or create a new issue. The more detailed context you provide about how you would use the feature, the more it will help us to support that feature in EVA.

📅 Release Cadence:

We tend to add features and fixes on a continuous iterative cycle and publish RC (Release Candidate) builds every 1-2 weeks. Once the amount of changes have reached a critical mass, we then go into a feature freeze for the upcoming version, address a final round of last-mile issues if any, run performance benchmarks and regression tests, continuously dog-food the builds and if everything looks good we do a final GA (Generally Available) release.

We do not have a fixed timeline for GA releases since we want final builds to be sufficiently tested and stable. That said, in the past we've done GA releases every 2-3 months.

georgia-tech-db / evadb