What's the plan for Superset 7.0? (roadmap, timeline, scope)

[anthonyhungnguyen]

What's the plan for Superset 7.0?

Hi all 👋

With 6.x now stable, I'd love to get a clearer picture of where Superset 7.0 is headed. I've gone through the public roadmap and the SIPs board but couldn't find a single consolidated answer, so hoping the maintainers/community can help.

Questions

1. Timeline — The release schedule lists 7.0 as first release H1 2026, EOL H2 2027. Is that still on track, and is there a target month / RC-cut date?
2. Scope / theme — What's the headline focus for 7.0? (e.g. continued design-system work post-AntD v5, performance, data model, async/SQL Lab, etc.)
3. Breaking changes — What major breaking changes or deprecations should operators plan for when upgrading 6.x → 7.0?
4. Tracking SIPs — Which SIPs / epics are currently tagged for the 7.0 milestone? Is there a board or label to follow?
5. How to help — Are there areas where community contributions would be most useful for hitting 7.0?

Context

• Current stable: 6.1.0
• I'm asking so we can plan our own upgrade timing and any contributions around it.

Thanks for any pointers — happy to help consolidate answers back into the roadmap docs if useful.

[anthonyhungnguyen]

@dosu could you give a first pass on this — current status, target timeline, and any SIPs tagged for the 7.0 milestone? Thanks!

[dosubot[bot]]

Hi @anthonyhungnguyen! I'm Dosu 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], 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]. However, the wiki also notes that releases may be delayed, accelerated, or altered in scope due to special circumstances [2]. 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 is the canonical place to track these, and version-specific planning boards are typically created closer to the release planning phase [3].

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]
• 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], 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].

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.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.