-1 due to the issues documented in the thread John linked. I encourage folks to test rc1 as long as the vote is open so that as many issues as possible are identified and we keep the number of release candidates to a minimum.
Thanks to Michael for leading this release process! On Fri, Dec 1, 2023, at 9:34 PM, John Bodley wrote: > -1 (binding) > > Per the discussion thread > <https://github.com/apache/superset/discussions/26118> there's already a > handful of issues detected including an Alembic migration ordering > issue—due to a picked cherry which went astray —which renders the > application unusable when upgrading from 3.0 to 3.1. > > On Tue, Nov 28, 2023 at 10:22 AM Michael S. Molina < > michael.s.mol...@gmail.com> wrote: > > > Hello Superset Community, > > > > This is a call for the vote to release Apache Superset version 3.1.0. > > > > The release notes: > > > > https://github.com/apache/superset/blob/master/RELEASING/release-notes-3-1/README.md > > > > The release candidate: > > https://dist.apache.org/repos/dist/dev/superset/3.1.0rc1/ > > > > Git tag for the release: > > https://github.com/apache/superset/tree/3.1.0rc1 > > > > The Change Log for the release: > > https://github.com/apache/superset/blob/3.1.0rc1/CHANGELOG.md > > > > The Updating instructions for the release: > > https://github.com/apache/superset/blob/3.1.0rc1/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 >
