-1

Looks like we'd probably want this in:
https://github.com/apache/superset/pull/33710 as it'll fix migrations

On Tue, Jun 10, 2025 at 8:24 PM Sam Firke <[email protected]> wrote:

> +1 (PMC binding)
>
> I finished my testing. Upgrading was smooth and there are some nice new
> features like controls for the rich tooltips introduced in 4.1!
>
> I filed a few minor bugs just now as issues on the 5.0.0 project board on
> GitHub. None are release-blocker-worthy in my opinion and I would defer to
> the release manager as to whether they're worth patching now or in a 5.0.1.
> I can support releasing rc3 as-is.
>
> Best,
>
> Sam
>
>
>
> On Mon, Jun 2, 2025, at 10:10 PM, Cubenshi Mimidenshi wrote:
> > Hello folks,
> >
> > I found no troubles migrating from 4.1.2 v with mysql db for metadata
> and bigquery and dremio for dw, so my non-binding vote is:
> >
> > + 1
> >
> >
> > ________________________________
> > De: Michael S. Molina <[email protected]>
> > Enviado: jueves, 29 de mayo de 2025 06:29 a. m.
> > Para: [email protected] <[email protected]>
> > Asunto: [VOTE] Release Apache Superset 5.0.0 based on Superset 5.0.0rc3
> >
> > Hello Superset Community,
> >
> > This is a call for the vote to release Apache Superset version 5.0.0.
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/superset/5.0.0rc3/
> >
> > The Git tag for the release:
> > https://github.com/apache/superset/tree/5.0.0rc3
> >
> > The CHANGELOG for the release:
> > https://github.com/apache/superset/blob/5.0.0rc3/CHANGELOG/5.0.0.md
> >
> > The instructions for updating to the release:
> > https://github.com/apache/superset/blob/5.0.0rc3/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
> >
>

Reply via email to