@Ville Brofeldt <[email protected]>, I'm wondering if this level of issue, arguably a priority P3 should warrant a new RC. I feel like we should accumulate more issues throughout the vote and sort out whether that batch of issues should hold up the RC or go into the next micro.
Or how about this! We could even just start a "DISCUSS" thread over a simple SHA or tag (no release work, just a simple email with a SHA id) and craft a proper RC Apache artifact with the resulting SHA + cherries once the DISCUSS thread settles (!?) On Fri, Oct 30, 2020 at 9:04 AM Ville Brofeldt <[email protected]> wrote: > Hi all, > > due to the regression discussed in > https://github.com/apache/incubator-superset/issues/11479 , I vote -1 > (binding) for rc1 and propose including > https://github.com/apache/incubator-superset/pull/11393 in rc2. > > Ville > > On 28. Oct 2020, at 20.19, Craig Rueda <[email protected]> wrote: > > +1 > > On Wed, Oct 28, 2020 at 7:22 AM daniel gaspar <[email protected]> > wrote: > > Hello Superset Community, > > This is a call for the vote to release Apache Superset > (incubating) version 0.38.0. > > The release candidate: > https://dist.apache.org/repos/dist/dev/incubator/superset/0.38.0rc1/ > > Git tag for the release: > https://github.com/apache/incubator-superset/tree/0.38.0rc1 > > The Change Log for the release: > https://github.com/apache/incubator-superset/blob/0.38.0rc1/CHANGELOG.md > > The Updating instructions for the release: > https://github.com/apache/incubator-superset/blob/0.38.0rc1/UPDATING.md > > public keys are available at: > > https://www.apache.org/dist/incubator/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 (Incubating) Team > > >
