I'm voting +1 on this release (PMC member = binding vote). I see there are still issues on the board for 6.0.0 and that a few cherries have been pulled into the 6.0 git branch since this release candidate was cut. But this release candidate meets the bar for a production release now, in my opinion.
That said, if others and especially the release manager are planning on an rc5 I would support that too. I'm excited to deploy this to production! Sam On Thu, Dec 4, 2025, at 4:37 PM, Sam Firke wrote: > Thanks Joe! > > Folks should know there are just thirteen commits to 6.0.0rc4 that weren't in > rc3. You can see them here: > https://github.com/apache/superset/commit/6a1c30e5e7c3e28d0549c9c2ac0ff61607f26a2f > > Or by running: > > git log --format="%h %s (%an)" 6.0.0rc3..6.0.0rc4 > > I will hold off voting until I can deploy and test just the areas that were > modified - but this looks promising! > > Sam > > On Thu, Dec 4, 2025, at 3:19 PM, Joe Li wrote: > > Hello Superset Community, > > > > This is a call for the vote to release Apache Superset version 6.0.0. > > > > The release candidate: > > https://dist.apache.org/repos/dist/dev/superset/6.0.0rc4/ > > > > The Git tag for the release: > > https://github.com/apache/superset/tree/6.0.0rc4 > > > > The CHANGELOG for the release: > > https://github.com/apache/superset/blob/6.0.0rc4/CHANGELOG/6.0.0.md > > > > The instructions for updating to the release: > > https://github.com/apache/superset/blob/6.0.0rc4/UPDATING.md > > > > Public keys are available at: > > https://www.apache.org/dist/superset/KEYS > > > > The vote will be left open until at least 72 hours have passed and the > > necessary number of votes (3) have been reached. > > > > Please vote accordingly: > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > Thanks, > > The Apache Superset Team > > >
