Signatures/keys all check out on the release candidate ✅ Seems to be running well via `docker compose` for me locally… not seeing anything busted in key workflows. ✅
+1, binding from where I sit. All the best, -e- Evan Rusackas Preset | preset.io Apache Superset PMC On Jun 17, 2025 at 11:48 AM -0600, Sam Firke <sfi...@apache.org>, wrote: > I tried testing docker compose deployment using the instructions on the > quickstart page (https://superset.apache.org/docs/quickstart) and it worked > for me: > > I ran: > git pull > git checkout tags/5.0.0rc3 > TAG=5.0.0rc3-dev docker compose -f docker-compose-image-tag.yml up > > And it was ready at http://localhost:8088. TAG=5.0.0rc3 also worked. > > Sam > > On 2025/06/12 15:22:45 Maxime Beauchemin wrote: > > light "-1" here as I tried to pull the branch and fire up `docker compose > > up` and getting some errors. I was surprised to see this as I would have > > thought CI should have failed. Maybe something related to my local env. > > [giving it another shot now .... will report back] > > [image: Screenshot 2025-06-12 at 8.16.57 AM.png] > > > > I tried a few things: > > - npm run prune, deleting caching folders and node_modules, running `npm ci` > > - confirmed that `docker-compose -f docker-compose-image-tag.yml up` works > > as expected ... > > > > On Wed, Jun 11, 2025 at 9:52 AM Joe Li <j...@preset.io.invalid> wrote: > > > > > -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 <s...@firke.com> 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 <michael.s.mol...@gmail.com> > > > > > Enviado: jueves, 29 de mayo de 2025 06:29 a. m. > > > > > Para: dev@superset.apache.org <dev@superset.apache.org> > > > > > 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 > > > > > > > > > > > > > > > > > > -- > > [image: twitter] <https://twitter.com/mistercrunch> > > [image: linkedin] <https://www.linkedin.com/in/maximebeauchemin/> > > Maxime Beauchemin > > > > Founder and CEO @ Preset > > m...@preset.io > > preset.io > >
