+1

On Mon, Apr 12, 2021 at 9:15 AM Erik Ritter <erik.t.rit...@gmail.com> wrote:

> +1 binding
>
> Verified that a release branch cut very close to the 1.1rc2 branch has no
> major regressions and deploys successfully at scale.
>
> Erik
>
> On Sat, Apr 10, 2021 at 7:39 AM Ville Brofeldt <ville.v.brofe...@gmail.com
> >
> wrote:
>
> > +1 binding
> >
> > Checked:
> >
> > - The release file is in the right location
> > - Signature and hash are correct.
> > - Version is correct in package.json
> > - Can build from source
> > - LICENSE and NOTICE file exist
> > - NOTICE year correct
> >
> > Ran the following test:
> > - installed built python binary by upgrading a pre-existing 1.0.1
> > deployment (with celery + redis)
> > - clicked through all dashboards (all charts rendered properly)
> > - accessed datasets on both sqlite and Postgres
> > - ran query and proceeded to explore the query
> > - synced columns on both physical and virtual dataset (updated properly)
> > - tested query with jinja expression (rendered property)
> >
> > Ville
> >
> > On 6. Apr 2021, at 0.17, b...@apache.org wrote:
> >
> > Hello Superset Community,
> >
> > This is a call for the vote to release Apache Superset version 1.1.0.
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/superset/1.1.0rc2/
> >
> > Git tag for the release:
> > https://github.com/apache/superset/tree/1.1.0rc2
> >
> > The Change Log for the release:
> > https://github.com/apache/superset/blob/1.1.0rc2/CHANGELOG.md
> >
> > The Updating instructions for the release:
> > https://github.com/apache/superset/blob/1.1.0rc2/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
> >
> >
> >
>

Reply via email to