GitHub user dosubot[bot] added a comment to the discussion: What's the plan for Superset 7.0? (roadmap, timeline, scope)
<!-- Answer --> Hi @anthonyhungnguyen! I'm [Dosu](https://go.dosu.dev/dosubot) and I'm helping the Apache Superset team. Here's what I was able to find: **Current Status:** The latest stable release is actually **5.0.0** (released June 18, 2025) [[1]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/CHANGELOG/5.0.0.md#L22), not 6.1.0 as mentioned in your post — so there may be some version numbering confusion worth clarifying with maintainers. **Timeline:** The release schedule wiki lists 7.0 as planned for **H1 2026**, with EOL in **H1 2027** [[2]](https://github.com/apache/superset/wiki/Release-Process). However, the wiki also notes that releases may be delayed, accelerated, or altered in scope due to special circumstances [[2]](https://github.com/apache/superset/wiki/Release-Process). No specific RC-cut date is published yet. **SIPs tagged for 7.0:** I couldn't find any SIPs or epics explicitly tagged for a 7.0 milestone at this time. The [SIPs Kanban board](https://github.com/orgs/apache/projects/170) is the canonical place to track these, and version-specific planning boards are typically created closer to the release planning phase [[3]](https://github.com/apache/superset/wiki/Release-Process). **Notable recent work that may land in a future major release:** - **Ant Design v5 migration** — a massive styling refactor (~1,267 files) introducing dynamic themes and dark mode [[4]](https://github.com/apache/superset/pull/31590) - **Extension framework** (`superset-core` packages) currently at 0.1.0-rc3, enabling custom backend/frontend extensions - **MCP integration** for AI-powered development tools **Breaking changes:** No 7.0-specific breaking changes are documented yet. The project tracks these in `UPDATING.md` [[5]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/UPDATING.md#L25-L31), but no 7.0 section exists. **How planning works:** Superset uses a structured process — proposed changes go through lazy consensus on the dev@ mailing list with a three-day objection period, and each major release gets a dedicated planning Kanban board where committers commit to release items [[3]](https://github.com/apache/superset/wiki/Release-Process). Given that detailed 7.0 planning doesn't appear to have started publicly yet, you may want to raise this on the dev@ mailing list or check in with maintainers directly for the most up-to-date information on scope and timeline. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).* --- Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset). [](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=7e4962e8-9b1d-481c-8113-024e9ccdc912) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset) GitHub link: https://github.com/apache/superset/discussions/40904#discussioncomment-17237974 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
