I am part way through testing and have found a couple of regressions from 4.0.0: https://github.com/apache/superset/issues/29342 - folks have been posting this one in Slack https://github.com/apache/superset/issues/29331 - this is trivial on its surface but as I've only just found it, don't know if it has other implications for broader functionality problems
I believe these are regressions from 4.0.0, so not problems introduced in *this *release. That said if they could be fixed, 4.0.2 would be a more stable release. Sam On Tue, Jun 18, 2024, at 9:42 AM, Michael S. Molina wrote: > Hello Superset Community, > > This is a call for the vote to release Apache Superset version 4.0.2. > > The release candidate: > https://dist.apache.org/repos/dist/dev/superset/4.0.2rc1/ > > The Git tag for the release: > https://github.com/apache/superset/tree/4.0.2rc1 > > The change log for the release: > https://github.com/apache/superset/blob/4.0.2rc1/CHANGELOG/4.0.2.md > > The instructions for updating to the release: > https://github.com/apache/superset/blob/4.0.2rc1/UPDATING.md > > Public keys are available at: > https://www.apache.org/dist/superset/KEYS > > The vote will be open for at least 72 hours or until the necessary number > of votes are reached. > > Please vote accordingly: > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Thanks, > The Apache Superset Team >