Community Update! 11/24

[Junlin Chen]

Dear community,

It’s time for the next Community Update! As mentioned in the last update,
this will be happening on a weekly basis.

To start, we would love to express our *appreciation* to some of the recent
contributions in Superset translation. Localization and translation
contribution is highly welcomed in Superset community, as they enables
Superset to serve bigger and wider user groups across the globe
🇦🇩🇧🇷🇦🇽🇧🇾🇦🇩🇨🇿🇧🇸🇭🇳🇲🇬
Milan Kriško (@minho95) - Slovakian
@dkrat7 - Slovenian
David Regla (@dreglad) - Spanish
Holger Bruch (@hbruch) - German
Augustin Doury(@audour) - French

*Thank you to everyone else *who has contributed last week in reporting
issues, bug fixes, typescript migration, database connection enhancement
etc. 🙏

*Community Survey*
We’re currently at 25 respondents. We’d like to analyze and release the
results once we’ve hit 100 people. *Please fill out the survey *if you
haven’t already, share it with others, and pass the word along! Unlike many
surveys, the insights will be used to directly improve the community &
project experience.
https://docs.google.com/forms/d/1tUXsyUfdGl1UDV3fDPjSJQEO-i_KXszG8HnxqMGIk6k/edit?ts=6192783b

*Feature discussion highlight*
You can help drive Superset roadmap by letting the community know what
feature or UI/UX enhancement should be included in near term development.
We highlight these two open issues and would love to see your comments!

[Prophet]Leverage predictive analytics to trigger alerts
https://github.com/apache/superset/issues/17510
[Explore] [Design] improving the experience when user creates a new chart
https://github.com/apache/superset/issues/17477

Superset *v1.4* is up for a vote! Please *help test the candidates* out and
let us know if anything important is missing.
https://github.com/apache/superset/releases/tag/1.4.0rc1
Discussion on Github: https://github.com/apache/superset/discussions/17528

*Upcoming Superset Events*
Dec 1st: Superset Contributor Bootcamp. In this guided session, we will
walk through end-to-end how to make your first contribution to the Apache
Superset project.
Sign up here:
https://us02web.zoom.us/webinar/register/WN_ZSK2wIg5QBW09_84JMGUAg

Best,
Superset Community Growth

Re: [VOTE][SIP-58] Proposal to move superset-ui to this repo, "Monorepo"

[Junlin Chen]

+1(binding) !! finally is happening!
Thank you, Yongjie for implementing the solutions, Ville for leading the
project, and both for improving Superset's developer's experience !


On Wed, Nov 3, 2021 at 12:15 PM Evan Rusackas  wrote:

> An emphatic +1 (binding)! This work would save countless hours of work,
> reduce various change management risks in superset, and hopefully increase
> organic contribution to the product. I’m excited!
>
> [X] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Evan Rusackas
> Preset | preset.io
>

Re: [VOTE][SIP-64] Migrate filter_box to Dashboard Native Filter Component

[Junlin Chen]

+1

On Wed, Oct 6, 2021 at 12:41 PM Grace Guo 
wrote:

> Hi Superset community,
>
> This is a call to vote for [SIP-64] Migrate filter_box to Dashboard Native
> Filter Component 
>
> The vote will be open for at least 1 week or until the necessary number of
> votes are reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> Grace Guo
>

Re: [VOTE] Release Apache Superset 1.3.1 based on Superset 1.3.1rc2

[Junlin Chen]

+1

On Wed, Sep 22, 2021 at 3:24 PM Maxime Beauchemin  wrote:

> +1
>
> On Wed, Sep 22, 2021 at 5:27 AM Ville Brofeldt  >
> wrote:
>
> > Hello Superset Community,
> >
> > This is a call for the vote to release Apache Superset version 1.3.1. New
> > cherries since 1.3.1rc1:
> >
> > - [#16711] feat(jinja): improve url parameter formatting (@villebro)
> > - [#14955] feat: show build number value in the About if present in the
> > config (@cccs-joel)
> > - [#16776] fix(dataset): retain is_dttm if set on metadata sync
> (@villebro)
> > - [#16716] fix(pandas-postprocessing): percentage compare to use correct
> > column (@villebro)
> > - [#16692] fix: catch exception when create connection (@zhaoyongjie)
> > - [#16699] fix(explore): only refresh data panel on relevant changes
> > (@villebro)
> > - [#16687] fix: don't send invalid URLs back to the user (@dpgaspar)
> > - [#16662] fix: fix assignment in FilterBoxViz (@tianhe1986)
> > - [#16634] fix(sqla): support for date adhoc filter (@villebro)
> > - [#16536] fix: params in sql lab are jumpy in the ace editor (@eschutho)
> > - [#16614] fix: TemporalWrapperType string representation (@villebro)
> > - [#16452] fix: queryEditor bug (@AAfghahi)
> > - [#16374] fix: update table ID in query context on chart import
> > (@betodealmeida)
> > - [#16289] fix: improve pivot post-processing (@betodealmeida)
> > - [#16262] fix: pivot col names in post_process (@betodealmeida)
> > - [#16702] perf(dashboard): native filter select will be stuck if there
> > has a filter box. (@stephenLYZ)
> > - [#16648] chore: Bump Flask-OpenID to 1.3.0 (@dpgaspar)
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/superset/1.3.1rc2/
> >
> > Git tag for the release:
> > https://github.com/apache/superset/tree/1.3.1rc2
> >
> > The Change Log for the release:
> > https://github.com/apache/superset/blob/1.3.1rc2/CHANGELOG.md
> >
> > The Updating instructions for the release:
> > https://github.com/apache/superset/blob/1.3.1rc2/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
>

Re: [VOTE] Release Apache Superset 1.3.0 based on Superset 1.3.0rc1

[Junlin Chen]

It would be nice to list the areas we tested in the RC while voting +1.

Given that we already have more than enough +1 to pass the vote while PM/QA
have not started the release testing yet. I am voting -1 to pause.



On Tue, Aug 10, 2021 at 11:29 PM Diego Pucci 
wrote:

> +1
>
> On Tue, Aug 10, 2021, 19:39 Michael S. Molina 
> wrote:
>
> > +1
> >
> > > On Aug 10, 2021, at 2:35 PM, Phillip Kelley-Dotson 
> > wrote:
> > >
> > >
> > >
> > > +1
> > >
> > >> On Aug 10, 2021, at 10:32 AM, Craig Rueda 
> wrote:
> > >>
> > >> +1
> > >>
> > >>> On Tue, Aug 10, 2021 at 9:41 AM Maxime Beauchemin 
> > wrote:
> > >>>
> > >>> +1 binding
> > >>>
> >  On Tue, Aug 10, 2021 at 1:37 AM Yongjie 
> > wrote:
> > 
> >  +1 binding
> > 
> >  On Tue, Aug 10, 2021 at 4:29 PM Ville Brofeldt <
> > >>> ville.v.brofe...@gmail.com
> > >
> >  wrote:
> > 
> > > Hello Superset Community,
> > >
> > > This is a call for the vote to release Apache Superset version
> 1.3.0.
> > >
> > > The release candidate:
> > > https://dist.apache.org/repos/dist/dev/superset/1.3.0rc1/
> > >
> > > Git tag for the release:
> > > https://github.com/apache/superset/tree/1.3.0rc1
> > >
> > > The Change Log for the release:
> > > https://github.com/apache/superset/blob/1.3.0rc1/CHANGELOG.md
> > >
> > > The Updating instructions for the release:
> > > https://github.com/apache/superset/blob/1.3.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
> > > --
> > 
> > >>>
> >
> >
>

[DISCUSS]Homepage UX changes

[Junlin Chen]

Hi community,

We will be implementing UI/UX changes on the Superset homepage. Details in
https://github.com/apache/superset/issues/15625
Please comment if you have any questions or concerns by *7/15.*
Change requests *after* 7/15 will be considered for the *next* iteration.

Thanks,
Junlin

[VOTE][SIP-67]: Gallery modal redesign and enhancement

[Junlin Chen]

This is a call to vote for SIP-67: Gallery modal redesign and enhancement
https://github.com/apache/superset/issues/14474

The vote will be open for at least 1 week or until the necessary number of
votes are reached.

Please vote accordingly:
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Thanks,
Junlin

Re: [VOTE] Release Apache Superset 1.2.0 based on Superset 1.2.0rc2

[Junlin Chen]

Hi Erik, These are old/cosmetic bugs, nothing blocking here, and the
majority of those will be fixed in 1.3. Let's move the release forward.

On Wed, Jun 9, 2021 at 7:33 AM Erik Ritter 
wrote:

> Quick question about the functional regressions Junlin:
>
> Are these regressions from 1.1? If so, then since they're known shouldn't
> we ensure they aren't broken in the 1.2 release? I would expect potential
> minor, unknown regressions in a new release (maybe something visual or an
> edge case) but not a release to go out with known, functional regressions.
> Thoughts?
>
> Erik
>
> On Tue, Jun 8, 2021 at 4:39 PM Junlin Chen  wrote:
>
> > +1
> > Many known functional regression like SORT control, backend pagination in
> > Table and visual regression - Tab and select component etc will be
> > addressed in v1.3(soon)
> >
> > The QA team @Rosemarie Chiu  (@rosemarie-chiu)
> > and @Jinghua
> > Yao  (@jinghua-qa) have put together a Superset
> release
> > sanity check test run
> > <
> >
> https://docs.google.com/spreadsheets/d/1ghbmLdCkoaykAnoHPWpeXt-ow_PLitgTCOwtZeNSKBI/edit#gid=0
> > >
> > for the community to participate in future Superset releases. 🙏
> > We are also in the process of improving spinning up the ephemeral
> > environments for community rc testing.
> > Participating in QA is a great way for non-technical community members to
> > contribute to the project, and we would love to see your feedback on how
> we
> > can improve the release process and quality of the product(by commenting
> in
> > the google sheet).
> >
> > thanks!
> >
> > On Mon, Jun 7, 2021 at 6:56 AM Ville Brofeldt <
> ville.v.brofe...@gmail.com>
> > wrote:
> >
> > > +1 (binding)
> > >
> > > Checked as follows,
> > >
> > > - Signature and hash are correct
> > > - Version is correct in package.json
> > > - LICENSE and NOTICE file exist
> > > - NOTICE year is correct
> > > - CHANGELOG.md contains entries for release
> > > - UPDATING.md contains entries for release
> > > - Can build from source
> > > - Can run examples
> > > - Can install via pip
> > >
> > > I also tested the following:
> > > - Add a new database
> > > - Click through the majority of example dashboards
> > > - Run a query is SQL Lab
> > > - Execute Jinja in query
> > > - Explore a virtual dataset
> > >
> > > Ville
> > >
> > > > On 25. May 2021, at 12.56, Amit Miran  wrote:
> > > >
> > > > Hello Superset Community,
> > > >
> > > > This is a call for the vote to release Apache Superset version 1.2.0.
> > > >
> > > > The release candidate:
> > > > https://dist.apache.org/repos/dist/dev/superset/1.2.0rc2/
> > > >
> > > > Git tag for the release:
> > > > https://github.com/apache/superset/tree/1.2.0rc2
> > > >
> > > > The Change Log for the release:
> > > > https://github.com/apache/superset/blob/1.2.0rc2/CHANGELOG.md
> > > >
> > > > The Updating instructions for the release:
> > > > https://github.com/apache/superset/blob/1.2.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
> > >
> > >
> >
>

Re: [VOTE] Release Apache Superset 1.2.0 based on Superset 1.2.0rc2

[Junlin Chen]

+1
Many known functional regression like SORT control, backend pagination in
Table and visual regression - Tab and select component etc will be
addressed in v1.3(soon)

The QA team @Rosemarie Chiu  (@rosemarie-chiu)
and @Jinghua
Yao  (@jinghua-qa) have put together a Superset release
sanity check test run

for the community to participate in future Superset releases. 🙏
We are also in the process of improving spinning up the ephemeral
environments for community rc testing.
Participating in QA is a great way for non-technical community members to
contribute to the project, and we would love to see your feedback on how we
can improve the release process and quality of the product(by commenting in
the google sheet).

thanks!

On Mon, Jun 7, 2021 at 6:56 AM Ville Brofeldt 
wrote:

> +1 (binding)
>
> Checked as follows,
>
> - Signature and hash are correct
> - Version is correct in package.json
> - LICENSE and NOTICE file exist
> - NOTICE year is correct
> - CHANGELOG.md contains entries for release
> - UPDATING.md contains entries for release
> - Can build from source
> - Can run examples
> - Can install via pip
>
> I also tested the following:
> - Add a new database
> - Click through the majority of example dashboards
> - Run a query is SQL Lab
> - Execute Jinja in query
> - Explore a virtual dataset
>
> Ville
>
> > On 25. May 2021, at 12.56, Amit Miran  wrote:
> >
> > Hello Superset Community,
> >
> > This is a call for the vote to release Apache Superset version 1.2.0.
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/superset/1.2.0rc2/
> >
> > Git tag for the release:
> > https://github.com/apache/superset/tree/1.2.0rc2
> >
> > The Change Log for the release:
> > https://github.com/apache/superset/blob/1.2.0rc2/CHANGELOG.md
> >
> > The Updating instructions for the release:
> > https://github.com/apache/superset/blob/1.2.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
>
>

SIPs in discussion

[Junlin Chen]

[SIP-60] Proposal to extend i18n support to charts

https://github.com/apache/superset/issues/13442
[SIP-62] Explore control panel Drag & Drop Interaction patterns and new
design  
https://github.com/apache/superset/issues/14114

Hi community,
Please provide your feedback on the above 2 SIPs, and let us know if you
would like to be part of the effort. :) Thanks!

Best,
Junlin

Re: [VOTE] Release Apache Superset 1.1.0 based on Superset 1.1.0rc1

[Junlin Chen]

Identified an issue during testing of 1.1/1.1.0 branches.
When clicking on 'Run in SQL Lab' from Explore in any
chart, flask.debughelpers.FormDataRoutingRedirect is returned and the whole
page crashed.
although there's a workaround, this button is quite commonly used... *I'm
inclined to have rc2. *
*thanks for testing *@Evan Rusackas *  and validating *@Phillip
Kelley-Dotson 

On Tue, Mar 30, 2021 at 5:59 PM Srinivasa Kadamati  wrote:

> Oh today I learned! Cool yeah we can add this for future releases  / in the
> template :)
>
> On Tue, Mar 30, 2021 at 8:52 PM Beto Dealmeida
>  wrote:
>
> > Thanks!
> >
> > (The email calling for the vote is autogenerated, and I think it might
> > be non-trivial to add the link to the release notes programmatically.)
> >
> >
> > On 3/30/21 5:04 PM, Srinivasa Kadamati wrote:
> > > We should also include the Release Notes
> > >
> > >
> >
> https://github.com/apache/superset/tree/1.1.0rc1/RELEASING/release-notes-1-1
> > >
> > >
> > > On Tue, Mar 30, 2021 at 5:25 PM  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.0rc1/
> > >>
> > >> Git tag for the release:
> > >> https://github.com/apache/superset/tree/1.1.0rc1
> > >>
> > >> The Change Log for the release:
> > >> https://github.com/apache/superset/blob/1.1.0rc1/CHANGELOG.md
> > >>
> > >> The Updating instructions for the release:
> > >> https://github.com/apache/superset/blob/1.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
> > >>
> >
>

Re: [VOTE] [SIP-61] Improve the organization of front-end folders

[Junlin Chen]

+1 binding

On Mon, Mar 29, 2021 at 10:02 PM Rob DiCiuccio  wrote:

> +1 binding
>
> On Mon, Mar 29, 2021 at 1:48 PM Evan Rusackas  wrote:
>
> > Hello Superset Community!
> >
> > This is a call to vote for SIP-61: Improve the organization of front-end
> > folders
> >
> > Further details here: https://github.com/apache/superset/issues/13632
> >
> > The vote will be open for at least 1 week or until the necessary number
> of
> > votes are reached.
> >
> > Please vote accordingly:
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Thank you!
> >
> > Evan Rusackas
> > Preset | preset.io
> > Apache Superset PMC
> >
> --
>
> *Rob DiCiuccio* (he/him)
> Director of Engineering
> Preset | https://preset.io
>

Re: [VOTE][SIP-59] Proposal for Database migration standards

[Junlin Chen]

+1.

On Wed, Mar 17, 2021 at 2:36 PM William Barrett  wrote:

> +1 (binding)
>
> Will Barrett
> Staff Software Engineer
> Preset, Inc. | https://preset.io
> On Mar 17, 2021, 1:20 PM -0700, Robert Stolz , wrote:
> > +1 (non-binding)
> >
> > On Wed, Mar 17, 2021 at 11:14 AM Phillip Kelley-Dotson <
> phil...@preset.io>
> > wrote:
> >
> > >
> > > +1
> > >
> > > > On Mar 17, 2021, at 11:10 AM, Maxime Beauchemin 
> wrote:
> > > >
> > > > +1
> > > >
> > > > > On Mon, Mar 15, 2021 at 7:04 PM Jesse Yang 
> wrote:
> > > > >
> > > > > +1 Binding
> > > > >
> > > > > Jesse
> > > > >
> > > > > > On Mar 15, 2021, at 5:54 PM, Erik Ritter <
> erik.t.rit...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > +1 (binding)
> > > > > >
> > > > > > Erik
> > > > > >
> > > > > > > On Mon, Mar 15, 2021 at 5:25 PM Bogdan Kyryliuk <
> b.kyryl...@gmail.com
> > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > +1, binding
> > > > > > >
> > > > > > > On Mon, Mar 15, 2021 at 5:22 PM Srinivasa Kadamati <
> sr...@preset.io>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > > On Mon, Mar 15, 2021 at 8:16 PM Beto Dealmeida
> > > > > > > >  wrote:
> > > > > > > >
> > > > > > > > > +1, binding
> > > > > > > > >
> > > > > > > > > On 3/15/21 5:00 PM, Craig Rueda wrote:
> > > > > > > > > > +1
> > > > > > > > > >
> > > > > > > > > > On Mon, Mar 15, 2021 at 4:46 PM Rob DiCiuccio <
> r...@preset.io>
> > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Superset Community,
> > > > > > > > > > >
> > > > > > > > > > > This is a call to vote for SIP-59: Proposal for
> Database migration
> > > > > > > > > > > standards
> > > > > > > > > > >
> > > > > > > > > > > Further details here:
> > > > > > > https://github.com/apache/superset/issues/13351
> > > > > > > > > > >
> > > > > > > > > > > The vote will be open for at least 1 week or until the
> necessary
> > > > > > > > number
> > > > > > > > > of
> > > > > > > > > > > votes are reached.
> > > > > > > > > > >
> > > > > > > > > > > Please vote accordingly:
> > > > > > > > > > > [ ] +1 approve
> > > > > > > > > > > [ ] +0 no opinion
> > > > > > > > > > > [ ] -1 disapprove with the reason
> > > > > > > > > > >
> > > > > > > > > > > Thank you!
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > >
> > > > > > > > > > > *Rob DiCiuccio* (he/him)
> > > > > > > > > > > Director of Engineering
> > > > > > > > > > > Preset | https://preset.io
> > > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Best regards,
> > > > > > > Bogdan Kyryliuk.
> > > > > > >
> > > > >
> > >
> >
> >
> > --
> > *Robert Stolz, Ph.D.*
> > he / him
> > Developer Advocate (Data Engineering)
> > Preset | preset.io
>

Re: [DISCUSS] Ephemeral environments via AWS ECS for Superset PRs

[Junlin Chen]

+1

On Thu, Feb 18, 2021 at 2:13 PM Maxime Beauchemin  wrote:

> +1
>
> On Thu, Feb 18, 2021 at 11:44 AM Bogdan Kyryliuk 
> wrote:
>
> > +1 binding, this will make testing so much easier, thanks !
> >
> > On Thu, Feb 18, 2021 at 10:58 AM Erik Ritter  > .invalid>
> > wrote:
> >
> > > +1 binding, thanks for sponsoring this and pushing it forward!
> > >
> > > Erik
> > >
> > > On Thu, Feb 18, 2021 at 10:52 AM William Barrett 
> wrote:
> > >
> > > > +1 binding
> > > >
> > > > Will Barrett
> > > > Staff Software Engineer
> > > > Preset, Inc. | https://preset.io
> > > > On Feb 18, 2021, 10:47 AM -0800, Rob DiCiuccio ,
> wrote:
> > > > > Hi all,
> > > > >
> > > > > This is a call for consensus for establishing the ability to create
> > > > > ephemeral test environments in the context of a Superset PR. This
> is
> > > > > required for an Apache INFRA request to add AWS account secrets to
> > the
> > > > > Superset repository.
> > > > >
> > > > > PR with full details:
> https://github.com/apache/superset/pull/13189
> > > > >
> > > > > Please respond to this thread using VOTE semantics (below), or any
> > > > > questions that can't be addressed directly on the PR.
> > > > >
> > > > > [ ] +1 approve
> > > > > [ ] +0 no opinion
> > > > > [ ] -1 disapprove with the reason
> > > > >
> > > > > Thank you!
> > > > > --
> > > > >
> > > > > *Rob DiCiuccio* (he/him)
> > > > > Director of Engineering
> > > > > Preset | https://preset.io
> > > >
> > >
> >
> >
> > --
> > Best regards,
> > Bogdan Kyryliuk.
> >
>

Re: [VOTE] Release Apache Superset 1.0.1 based on Superset 1.0.1rc2

[Junlin Chen]

Hi Byran,
Thanks for bringing up this issue. We are aware of it and are planning to
do a thorough audit to go over all chart control panels and build query
code to ensure we get the "order by" control to all charts, which will take
a week or so to finish.
I don't think the community should wait longer for v1.0.1 patch, given 1)
quite a few fixes for v1.0 need to get out soon 2)master is not in its best
shape .

We have prioritized the ORDER BY issue, and will do a fast follow with
v1.0.2. We apologize for the inconvenience! 🙏

+1 on rc2

-junlin

On Thu, Feb 4, 2021 at 8:21 AM Bryan Keller  wrote:

> -1
>
> The word cloud chart and line chart with group by have a similar lack of
> "order by" issue that the bar chart had. I feel this regression from
> earlier versions is serious enough that a fix should be included.
>
> (For reference, see https://github.com/apache/superset/pull/12674 <
> https://github.com/apache/superset/pull/12674>)
>
>
> > On Feb 2, 2021, at 11:12 AM, Ville Brofeldt 
> wrote:
> >
> > Hello Superset Community,
> >
> > This is a call for the vote to release Apache Superset version 1.0.1. The
> > second release candidate includes the following cherries on top of the
> ones
> > featured in rc1:
> > - feat(release): add github token to changelog script (#12872)
> (@dpgaspar)
> > - fix: allow users to reset their passwords (#12886) (@dpgaspar)
> > - fix(menu): always show settings dropdown (#12877) (@nytai)
> > - fix(release): add typing-extensions as dependency (#12648) (@villebro)
> > - fix: Presto column_type_mappings time and timestamp (#12861)
> (@rmgpinto)
> > - fix: bar chart data order (#12665) (@kstrz)
> > - add order by for bar charts (#12661) (@bryanck)
> >
> > Big thanks to everyone who participated in testing the release candidate,
> > reporting issues and fixing bugs!
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/superset/1.0.1rc2/
> >
> > Git tag for the release:
> > https://github.com/apache/superset/tree/1.0.1rc2
> >
> > The Change Log for the release:
> > https://github.com/apache/superset/blob/1.0.1rc2/CHANGELOG.md
> >
> > The Updating instructions for the release (no changes since 1.0.0):
> > https://github.com/apache/superset/blob/1.0.1rc2/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
>
>

Unstable master

[Junlin Chen]

Hi community,

We have noticed some regressions in master that are causing inaccurate data
showing. We are currently working on the fixes. Please stay on v1.0 or wait
for the patch release v1.0.1 if you can 🙏. Sorry about the inconvenience.

Thanks,
-junlin

Re: [VOTE] Release Apache Superset 1.0.1 based on Superset 1.0.1rc1

[Junlin Chen]

Tested again and confirmed that the severe regression is not in v1.0(as
reported https://github.com/apache/superset/issues/12853), only in master.
we have pushed a fix, both cause and fix will not affect v1.0.1 rc1.. sorry
about the confusion!
revote +1



On Sun, Jan 31, 2021 at 10:29 PM Junlin Chen  wrote:

> -1
>
> we are working on a severe regression. need to get this one in the patch
> release.
> https://github.com/apache/superset/issues/12853
>
> On Sat, Jan 30, 2021 at 10:36 PM Bence Orlai  wrote:
>
>> + 1
>>
>> On Sat, Jan 30, 2021, 11:05 AM Ville Brofeldt > >
>> wrote:
>>
>> > Hello Superset Community,
>> >
>> > This is a call for the vote to release Apache Superset version 1.0.1.
>> > This release includes fixes to all known critical bugs observed in
>> > version 1.0.0, along with several usability improvements.
>> >
>> > The release candidate:
>> > https://dist.apache.org/repos/dist/dev/superset/1.0.1rc1/
>> >
>> > Git tag for the release:
>> > https://github.com/apache/superset/tree/1.0.1rc1
>> >
>> > The Change Log for the release:
>> > https://github.com/apache/superset/blob/1.0.1rc1/CHANGELOG.md
>> >
>> > The Updating instructions for the release (no changes since 1.0.0):
>> > https://github.com/apache/superset/blob/1.0.1rc1/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
>> > --
>>
>

Re: [VOTE] Release Apache Superset 1.0.1 based on Superset 1.0.1rc1

[Junlin Chen]

-1

we are working on a severe regression. need to get this one in the patch
release.
https://github.com/apache/superset/issues/12853

On Sat, Jan 30, 2021 at 10:36 PM Bence Orlai  wrote:

> + 1
>
> On Sat, Jan 30, 2021, 11:05 AM Ville Brofeldt 
> wrote:
>
> > Hello Superset Community,
> >
> > This is a call for the vote to release Apache Superset version 1.0.1.
> > This release includes fixes to all known critical bugs observed in
> > version 1.0.0, along with several usability improvements.
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/superset/1.0.1rc1/
> >
> > Git tag for the release:
> > https://github.com/apache/superset/tree/1.0.1rc1
> >
> > The Change Log for the release:
> > https://github.com/apache/superset/blob/1.0.1rc1/CHANGELOG.md
> >
> > The Updating instructions for the release (no changes since 1.0.0):
> > https://github.com/apache/superset/blob/1.0.1rc1/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
> > --
>

Re: [DISCUSS] Superset design proposal tagging system

[Junlin Chen]

Thank you, Mihir, for bringing more Design presence to the Superset open
source community! Both of your latest design proposals-Explore redesign and
Capitalization are very valuable and they landed pretty nicely.

A few questions that come to mind
How do we define whether an issue is "settled" or not? Should we utilize
the voting mechanism same as SIP?
If we have a different mechanism, how do we weigh opinions from committers
vs. general users?
How should we address future comments and concerns from people who weren't
a part of the previous discussion after a guideline is settled in wiki? Do
we reopen the discussion?

thanks,
-junlin

On Tue, Jan 26, 2021 at 4:49 PM Mihir Chahuan  wrote:

> Hi everyone,
>
> We want to implement a new way of bringing small design proposals to the
> community on an ongoing basis, for discussion, and then addition to the
> wiki. The flow will be as follows, if all agree:
>
> 1) Design proposals will be written up as Github Issues with the
> `design:proposal` tag.
> 2) Design proposals will remain open for 3 days, or longer if contention
> arises in the thread. In that event, a [DISCUSS] thread can be sent here on
> the dev list, to draw attention/comments to the GitHub issue.
> 3) When the issue settles on Github (after 3 days, by default), the result
> will be added to the Wiki
>  in the
> upcoming Design Guidelines section
> .
>
> These UI copy capitalization guidelines
> <
> https://github.com/apache/superset/blob/master/CONTRIBUTING.md#capitalization-guidelines
> >
> are
> an example of a design guideline that can be added to the Wiki.
>
> Not every design proposal will result in a design guideline on the wiki,
> but we wanted to establish a proposal for how things can arrive on the wiki
> with due process.
>
> Let me know what you think!
>
> Thanks,
> Mihir
>

Re: [VOTE] Release Apache Superset 1.0.0 based on Superset 1.0.0rc4

[Junlin Chen]

After three failed attempts, we decided to kick off the rc4 vote by knowing
1) all the p0 & p1 issues have been resolved, 2) with all the effort we
included in the last few rounds, Superset IS at its best state in history
since its inception.
As the PM for Superset, as much as I would like to get Superset to a
“Perfect State” by 1.0, I hope that the product can keep reaching its
milestones and be known and adopted by a broader range of users.
(More importantly, to keep the 1.0 release team and our P0 heroes sane 🙏.
Huge thanks to Ville, Jesse, Evan, Beto and Yongjie! )

We appreciate all the testing effort and feedback from the community. We
are committed to addressing the rest of the filed and new issues on GitHub,
continually improving our product to meet users’ needs.

Thus, I’m voting *+1* for rc4. I hope, after all the great work we had put
in, the vote can finally pass at the fourth attempt.

-junlin

On Fri, Jan 15, 2021 at 10:28 PM Ville Brofeldt 
wrote:

> Hello Superset Community,
>
> This is a call for the vote to release Apache Superset version 1.0.0.
> All reported critical bugs in 1.0.0rc3 have been addressed.
> The full list of PRs added since 1.0.0rc3 are as follows:
> - Fix 500 error when loading dashboards with slice having deleted dataset
> (#12535) (@bechob)
> - fix: case expression should not have double quotes (#12562)
> (@betodealmeida)
> - fix: height on grid results (#12558) (@betodealmeida)
> - fix(viz): missing groupby and broken adhoc metrics for boxplot (#12556)
> (@ktmud)
> - fix: Add MAX_SQL_ROW value to LIMIT_DROPDOWN (#12555) (@hug)
> - fix: Popover closes on change of dropdowns values (#12410) (@geido)
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/superset/1.0.0rc4/
>
> Git tag for the release:
> https://github.com/apache/superset/tree/1.0.0rc4
>
> The Change Log for the release:
> https://github.com/apache/superset/blob/1.0.0rc4/CHANGELOG.md
>
> The Updating instructions for the release:
> https://github.com/apache/superset/blob/1.0.0rc4/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
> --
>

Re: [VOTE] Release Apache Superset 1.0.0 based on Superset 1.0.0rc3

[Junlin Chen]

agreed
-1

let's try again with all p0 p1 issues resolved

On Fri, Jan 15, 2021 at 9:49 AM Erik Ritter  wrote:

> FYI, it looks like there's a fairly serious bug with the Box Plot viz type:
> https://github.com/apache/superset/issues/12553. Do folks think this
> should
> block 1.0.0? It seems pretty bad to me...
>
> Erik
>
> On Fri, Jan 15, 2021 at 9:29 AM Maxime Beauchemin  wrote:
>
> > Quick note here that we'd love to push this through so that it's ready
> for
> > the ASF graduation announcement on the 19th (coordinated by Sally @
> > Apache), so please test! but let's keep "-1" votes for super high
> priority
> > issues ("P0" and highly visible "P1").
> >
> > We can commit to fast-follow 1.0.0 with a 1.0.1 as well to handle the
> >=P2
> > issues
> >
> > If we need an RC4 we'll have to move fast! OR perhaps delay the
> > announcement :(
> >
> > Max
> >
> > On Fri, Jan 15, 2021 at 8:33 AM Ville Brofeldt <
> ville.v.brofe...@gmail.com
> > >
> > wrote:
> >
> > > Hello Superset Community,
> > >
> > > This is a call for the vote to release Apache Superset version 1.0.0.
> > > All reported critical bugs in 1.0.0rc2 have been addressed.
> > > The full list of PRs added since 1.0.0rc2 are as follows:
> > > - chore: rename docker image from incubator-superset to superset
> (#1337)
> > > (@amitmiran137)
> > > - feat(db-engine): Add support for Apache Solr (#12403) (@aadel)
> > > - Fix list filters vertical alignment (#12497) (@michael-s-molina)
> > > - fix: Select options overflowing Save chart modal on Explore view
> > > (#12522) (@kgabryje)
> > > - Fixing Pinot queries for time granularities:
> > WEEKS/MONTHS/QUARTERS/YEARS
> > > (#12536) (@fx19880617)
> > > - fix(explore): Add Time section back to FilterBox (#12537) (@ktmud)
> > > - fix(explore): time table control panel (#12532) (@ktmud)
> > > - fix: lowercase all columns in examples (#12530) (@betodealmeida)
> > > - ci: remove refs/tags from docker tags on a release (#12518)
> (@dpgaspar)
> > > - fix: impose dataset ownership check on old API (#12491) (@dpgaspar)
> > >
> > > The release candidate:
> > > https://dist.apache.org/repos/dist/dev/superset/1.0.0rc3/
> > >
> > > Git tag for the release:
> > > https://github.com/apache/superset/tree/1.0.0rc3
> > >
> > > The Change Log for the release:
> > > https://github.com/apache/superset/blob/1.0.0rc3/CHANGELOG.md
> > >
> > > The Updating instructions for the release:
> > > https://github.com/apache/superset/blob/1.0.0rc3/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
> > > --
> > >
> >
>

Re: [VOTE] Release Apache Superset 1.0.0 based on Superset 1.0.0rc1

[Junlin Chen]

rolling back my +1,

-1 on rc1! In light of issues surfaced by the community, I agree that we
should fix the below and other issues raised in sql-lab first.

[Explore]Blank deck.gl Multiple Layers chart control(Old issue)
<https://github.com/apache/superset/issues/12427>
[chart]MultiLine is BROKEN(again) and is incompatible with async queries
<https://github.com/apache/superset/issues/12329>


On Mon, Jan 11, 2021 at 3:56 PM Maxime Beauchemin  wrote:

> Calling to action everyone who can help us test 1.0.x! Please open GitHub
> issue and reference it in this thread
>
> Keep in mind that:
> - as much as possible, we'd like to stick with January 19th as the
> announcement since we're coordinating with the ASF PR
> - we can push 1.0.1 very soon after 1.0.0, so we may deflect P2s and P3s
> onto that next release to ensure that we have an official release out by
> the 19th (or very soon after)
> - we're holding back on merging non-1.0-related PRs into master for now, so
> that master and the 1.0 release branch are effectively one and the same for
> the time being to keep things simple and focussed
>
> Max
>
> On Mon, Jan 11, 2021 at 12:09 PM Tai Dupree  wrote:
>
> > @junlin can you post which PRs need reviewing?
> >
> > On Mon, Jan 11, 2021 at 11:49 AM Junlin Chen  wrote:
> >
> > > @jesse.y...@airbnb.com  yes,these two p1&p2
> fixes
> > > should be included in the rc2!!
> > > we have 6 more open PRs should get in rc2 as well! please help
> reviewing
> > > testing merging🙏
> > >
> > >
> > >
> > > On Mon, Jan 11, 2021 at 11:41 AM Jesse Yang  wrote:
> > >
> > > > -1.
> > > >
> > > > Super exciting progress and can't wait to get this out!
> > > >
> > > > But there are a couple of bugs that have already been fixed or in
> > review,
> > > > e.g.
> > > >
> > > > - https://github.com/apache/superset/pull/12406
> > > > - https://github.com/apache/superset/pull/12387
> > > >
> > > > It would be nice to have them in the official 1.0.0 release since the
> > > work
> > > > is already done.  Let's keep testing and prepare for RC2!
> > > >
> > > >
> > > > Thanks,
> > > > Jesse
> > > >
> > > > > On Jan 11, 2021, at 11:31 AM, Maxime Beauchemin <
> > > > maximebeauche...@gmail.com> wrote:
> > > > >
> > > > > +1
> > > > >
> > > > > !!!
> > > > >
> > > > >
> > > > > On Mon, Jan 11, 2021 at 8:06 AM Anna Kepler  >
> > > > wrote:
> > > > >
> > > > >> +1
> > > > >>
> > > > >> On Mon, Jan 11, 2021 at 9:48 AM Srinivasa Kadamati <
> sr...@preset.io
> > >
> > > > >> wrote:
> > > > >>
> > > > >>> +1 , super excited!
> > > > >>>
> > > > >>> On Mon, Jan 11, 2021 at 8:31 AM William Barrett 
> > > > wrote:
> > > > >>>
> > > > >>>> +1
> > > > >>>>
> > > > >>>> Will Barrett
> > > > >>>> Staff Software Engineer
> > > > >>>> Preset, Inc. | https://preset.io
> > > > >>>> On Jan 10, 2021, 11:21 PM -0800, Bence Orlai ,
> > > > wrote:
> > > > >>>>> +1
> > > > >>>>>
> > > > >>>>> On Mon, Jan 11, 2021, 3:12 AM yongjie zhao <
> > yongjie.z...@gmail.com
> > > >
> > > > >>>> wrote:
> > > > >>>>>
> > > > >>>>>> +1
> > > > >>>>>>
> > > > >>>>>> On Mon, Jan 11, 2021 at 9:19 AM Craig Rueda <
> > cr...@craigrueda.com
> > > >
> > > > >>>> wrote:
> > > > >>>>>>
> > > > >>>>>>> +1
> > > > >>>>>>>
> > > > >>>>>>> - Craig
> > > > >>>>>>>
> > > > >>>>>>>> On Jan 10, 2021, at 4:16 PM, Junlin Chen 
> > > > >>> wrote:
> > > > >>>>>>>>
> > > > >>>>>>>> +1!
> > > > >>>>>>>>
> > > > >>>>>>>>
> >

Re: [VOTE] Release Apache Superset 1.0.0 based on Superset 1.0.0rc1

[Junlin Chen]

@jesse.y...@airbnb.com  yes,these two p1&p2 fixes
should be included in the rc2!!
we have 6 more open PRs should get in rc2 as well! please help reviewing
testing merging🙏



On Mon, Jan 11, 2021 at 11:41 AM Jesse Yang  wrote:

> -1.
>
> Super exciting progress and can't wait to get this out!
>
> But there are a couple of bugs that have already been fixed or in review,
> e.g.
>
> - https://github.com/apache/superset/pull/12406
> - https://github.com/apache/superset/pull/12387
>
> It would be nice to have them in the official 1.0.0 release since the work
> is already done.  Let's keep testing and prepare for RC2!
>
>
> Thanks,
> Jesse
>
> > On Jan 11, 2021, at 11:31 AM, Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
> >
> > +1
> >
> > !!!
> >
> >
> > On Mon, Jan 11, 2021 at 8:06 AM Anna Kepler 
> wrote:
> >
> >> +1
> >>
> >> On Mon, Jan 11, 2021 at 9:48 AM Srinivasa Kadamati 
> >> wrote:
> >>
> >>> +1 , super excited!
> >>>
> >>> On Mon, Jan 11, 2021 at 8:31 AM William Barrett 
> wrote:
> >>>
> >>>> +1
> >>>>
> >>>> Will Barrett
> >>>> Staff Software Engineer
> >>>> Preset, Inc. | https://preset.io
> >>>> On Jan 10, 2021, 11:21 PM -0800, Bence Orlai ,
> wrote:
> >>>>> +1
> >>>>>
> >>>>> On Mon, Jan 11, 2021, 3:12 AM yongjie zhao 
> >>>> wrote:
> >>>>>
> >>>>>> +1
> >>>>>>
> >>>>>> On Mon, Jan 11, 2021 at 9:19 AM Craig Rueda 
> >>>> wrote:
> >>>>>>
> >>>>>>> +1
> >>>>>>>
> >>>>>>> - Craig
> >>>>>>>
> >>>>>>>> On Jan 10, 2021, at 4:16 PM, Junlin Chen 
> >>> wrote:
> >>>>>>>>
> >>>>>>>> +1!
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> On Sun, Jan 10, 2021 at 4:03 PM Eugenia Moreno <
> >>>> euge...@preset.io>
> >>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>> +1!!
> >>>>>>>>>
> >>>>>>>>> On Sat, Jan 9, 2021 at 5:22 PM Ville Brofeldt <
> >>>>>>> ville.v.brofe...@gmail.com>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> Hello Superset Community,
> >>>>>>>>>>
> >>>>>>>>>> This is a call for the vote to release Apache Superset
> >>> version
> >>>> 1.0.0.
> >>>>>>>>>> A significant amount of work has gone into crafting this
> >>>> release
> >>>>>>>>> candidate,
> >>>>>>>>>> with several new features, usability improvements and bug
> >>> fixes
> >>>>>>>>> introduced
> >>>>>>>>>> since
> >>>>>>>>>> the last release (0.38.0). Please take the time to test
> >> this
> >>>> release
> >>>>>>>>>> candidate and
> >>>>>>>>>> report any problems you may encounter so that we can
> >> release
> >>>> the best
> >>>>>>>>>> version
> >>>>>>>>>> of Superset to date!
> >>>>>>>>>>
> >>>>>>>>>> The release candidate:
> >>>>>>>>>> https://dist.apache.org/repos/dist/dev/superset/1.0.0rc1/
> >>>>>>>>>>
> >>>>>>>>>> Git tag for the release:
> >>>>>>>>>> https://github.com/apache/superset/tree/1.0.0rc1
> >>>>>>>>>>
> >>>>>>>>>> The Change Log for the release:
> >>>>>>>>>>
> >>> https://github.com/apache/superset/blob/1.0.0rc1/CHANGELOG.md
> >>>>>>>>>>
> >>>>>>>>>> The Updating instructions for the release:
> >>>>>>>>>>
> >> https://github.com/apache/superset/blob/1.0.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
> >>>>>>>>>> --
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Eugenia Moreno <
> >>> https://www.linkedin.com/in/eugeniamorenozerdan>
> >>>>>>>>> *Customer Engagement*
> >>>>>>>>> *Preset.io* <http://preset.io/>
> >>>>>>>>> Book Time with me <https://meetings.hubspot.com/eugenia5>
> >>>>>>>>> C: 617-633-7641
> >>>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>
> >>>
> >>
>
>

Re: [VOTE] Release Apache Superset 1.0.0 based on Superset 1.0.0rc1

[Junlin Chen]

+1!


On Sun, Jan 10, 2021 at 4:03 PM Eugenia Moreno  wrote:

> +1!!
>
> On Sat, Jan 9, 2021 at 5:22 PM Ville Brofeldt 
> wrote:
>
> > Hello Superset Community,
> >
> > This is a call for the vote to release Apache Superset version 1.0.0.
> > A significant amount of work has gone into crafting this release
> candidate,
> > with several new features, usability improvements and bug fixes
> introduced
> > since
> > the last release (0.38.0). Please take the time to test this release
> > candidate and
> > report any problems you may encounter so that we can release the best
> > version
> > of Superset to date!
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/superset/1.0.0rc1/
> >
> > Git tag for the release:
> > https://github.com/apache/superset/tree/1.0.0rc1
> >
> > The Change Log for the release:
> > https://github.com/apache/superset/blob/1.0.0rc1/CHANGELOG.md
> >
> > The Updating instructions for the release:
> > https://github.com/apache/superset/blob/1.0.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
> > --
>
> --
> Eugenia Moreno 
> *Customer Engagement*
> *Preset.io* 
> Book Time with me 
> C: 617-633-7641
>

Re: [DISCUSS] Enable GitHub Discussions?

[Junlin Chen]

+1

-junlin

On Sun, Dec 13, 2020 at 5:45 PM Maxime Beauchemin  wrote:

> +1 even if just to [DISCUSS] SIPs in place of using issues as a starting
> point. Personally I much prefer this to mailing list because it offers:
>
> - subscribe/unsubscribe on a per-discussion basis (manage signal/noise
> ratio)
> - reactions
> - rich integration with issues/PRs, code
> - markdown support for rich formatting
> - searchability, categorization (labels, actors, time range, ...)
> - decent SEO (guessing it'll work better than ponymail)
> - analytics through the REST API sync
> - ...
>
> Max
>
> On Sat, Dec 12, 2020 at 10:31 PM Jesse Yang  wrote:
>
> > Dear Superset community,
> >
> > During the last Superset meetup, we had a discussion on GitHub
> Discussions
> > <
> >
> https://github.blog/2020-05-06-new-from-satellite-2020-github-codespaces-github-discussions-securing-code-in-private-repositories-and-more/
> >.
> > This is a feature GitHub announced in May which has been in open beta for
> > the last couple of months. Many open source projects have since adopted
> it
> > (including some apache projects, Airflow <
> > https://github.com/apache/airflow/discussions>, Couchdb <
> > https://github.com/apache/couchdb/discussions>, MXNet <
> > https://github.com/apache/incubator-mxnet/discussions>, and many others
> > such as Next.js , Gatsby
> <
> > https://github.com/gatsbyjs/gatsby/discussions> and Strapi <
> > https://github.com/strapi/strapi/discussions>).
> >
> > With Github Discussions, users can start casual conversations, ask
> > questions and get help from the community in a discussion board, similar
> to
> > what they are now able to do with Slack <
> >
> https://apache-superset.slack.com/join/shared_invite/zt-g8lpruog-HeqpgYrwdfrD5OYhlU7hPQ#/
> >,
> > StackOverflow <
> > https://stackoverflow.com/questions/tagged/superset+apache-superset>, or
> > this mailing list.
> >
> > The main difference is that Discussions is more tightly integrated with
> > the GitHub repo and a developer's everyday workflow therefore more
> > accessible and discoverable. It has many useful features such as
> > categories, upvotes and indented thread view, which all makes organizing
> > and discovering conversations easier. By moving casual conversations to a
> > new forum, it also frees up GitHub Issues for actual TODOs and bug
> reports
> > so that committers can track work progress more efficiently.
> >
> > This email is a call for discussion/vote on whether we should enable this
> > feature for Superset. Note that per Apache policy, such forum "can only
> be
> > used for user help issues, all code-related discussions and project
> > management activities (will still) be reflected to an ASF mailing list"
> > [1]. During the meetup, someone also raised the concern that this new
> venue
> > of conversations may split committer attention and lead to slower
> > responses. But one may argue since developers already use GitHub
> everyday,
> > the attention may not split that much anyway. Other than that, I
> personally
> > don't see any major downside.
> >
> > Please feel free to voice your support or concerns one way or another.
> >
> >
> > Thanks,
> > Jesse
> >
> > [1] https://issues.apache.org/jira/browse/INFRA-20772 <
> > https://issues.apache.org/jira/browse/INFRA-20772>
>

[DISCUSS] centralizing issues in the main repo

[Junlin Chen]

Hi all,

A few of us have been monitoring our main repo incubator-superset/issues 
closely to improve efficiency and velocity lately. As a result, we are able to 
resolve most of the regression bugs within days and get to questions and 
requests from community members within hours. While the triage team focuses on 
the main repo, issues posted in other repos have not been picked up timely.

To ensure all issues are being addressed in time, I am opening this thread to 
discuss centralizing all issues in the main repo moving forward, which I highly 
encourage community members to do so. 
Thanks so much! 

Best,
Junlin 
PM(Data Viz)
Preset | preset.io

Re: Upcoming committers meetup Friday @ noon (PST)

[Junlin Chen]

As we are becoming more inclusive and opening these meetings to the
community and a broader audience, should we also consider changing the
meeting time that works for folks from Europe, Asia and the Middle-east?

Thanks,
Junlin

On Tue, Oct 13, 2020 at 11:19 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Superset community,
>
> As many of you are already aware, some committers/PMC/contributors get
> together every two weeks, usually on Friday or Thursday to [DISCUSS]
> ongoing important issues and development taking place. The agenda is
> submitted ahead of the meeting by the attendees, and we try to cover all
> the topics submitted.
>
> In an effort to be more inclusive, we'd like to extend the invitation to
> the community, and to consistently make our notes available. To get a sense
> of the kind of topics that we cover, you can explore the notes from
> previous meetings here:
>
> https://docs.google.com/document/d/1xRLqmUn-G7WiPe8qZnfuvbrYHZ1jmk9aSv9Bhjis2tg/edit#
> <
> https://www.google.com/url?q=https://docs.google.com/document/d/1xRLqmUn-G7WiPe8qZnfuvbrYHZ1jmk9aSv9Bhjis2tg/edit%23&sa=D&source=calendar&ust=1603066196918000&usg=AOvVaw2KkTI_iTNQr0UZi3dBYHi4
> >
>
> I'm also sending this note as a reminder to attendees to avoid decision
> making during these sessions, and to bring back important information and
> votes to the dev@ mailing list.
>
> Let us know if you'd like to be added to the recurring invite.
>
> Thanks,
>
> Max
>

Re: GitHub "triage" role for PMs & active contributors

[Junlin Chen]

Zuzana and I had finished creating the new labels
<https://docs.google.com/spreadsheets/d/1Q4drasrib1Ciphteq-5fDbD1iDaVafkCdnrzojMavD0/edit#gid=0>for
GitHub issues but needed help from a committee to upload them.

The triage role does not allow adding, deleting, or editing existing
labels. Can someone from PPMC help finish the process?

Thanks,
Junlin

On Thu, Sep 24, 2020 at 9:40 AM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Related to this topic, I heard that the triage role allows for labeling but
> not "bulk-labeling" which is a tiny bit tragic :(
>
> Max
>
> On Thu, Sep 24, 2020 at 9:39 AM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
> > Please try to reopen the Jira issue linked above or reopen a new one with
> > your name.
> >
> > On Wed, Sep 23, 2020 at 12:59 AM Furkan KAMACI 
> > wrote:
> >
> >> HI,
> >>
> >> I would like to be added too. My GitHub account is: *kamaci*
> >>
> >> Kind Regards,
> >> Furkan KAMACI
> >>
> >> On Wed, Sep 23, 2020 at 10:40 AM Katarzyna Kucharczyk <
> >> ka.kucharc...@gmail.com> wrote:
> >>
> >> > Thank you Max, it works for me. Is it possible to add Kamil
> Gabryjelski
> >> > (kgabryje) and Adam Stasiak (adam-stasiak) as well?
> >> >
> >> > Kasia
> >> >
> >> > On Tue, Sep 22, 2020 at 2:50 AM Maxime Beauchemin 
> >> wrote:
> >> >
> >> > > Apache INFRA reports to have created the role and assigned it:
> >> > >
> >> > >
> >> >
> >>
> https://issues.apache.org/jira/browse/INFRA-20853?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
> >> > >
> >> > > People on the list, let me know if that worked!
> >> > >
> >> > > Max
> >> > >
> >> > > On Wed, Sep 16, 2020 at 10:31 AM Junlin Chen 
> >> wrote:
> >> > >
> >> > > > Zuzana(zuzana-vej) and I(JunlinC) volunteer to help cleanup the
> >> > existing
> >> > > > labels and issues, and put together a labeling guideline for the
> >> > > community.
> >> > > > Thanks!
> >> > > >
> >> > > > On Tue, Sep 15, 2020 at 10:51 AM Eugenia Moreno <
> euge...@preset.io>
> >> > > wrote:
> >> > > >
> >> > > > > eugeniamz please!
> >> > > > >
> >> > > > > On Tue, Sep 15, 2020 at 1:48 PM Srinivasa Kadamati <
> >> sr...@preset.io>
> >> > > > > wrote:
> >> > > > >
> >> > > > > > Good call Max, I'm in (and I want to onboard the Champions
> next
> >> > week
> >> > > > > too):
> >> > > > > > *srinify*
> >> > > > > >
> >> > > > > > On Tue, Sep 15, 2020 at 1:39 PM Rob DiCiuccio 
> >> > wrote:
> >> > > > > >
> >> > > > > > > Yes please: robdiciuccio
> >> > > > > > >
> >> > > > > > > On Mon, Sep 14, 2020 at 9:27 PM Maxime Beauchemin <
> >> > > > > > > maximebeauche...@gmail.com> wrote:
> >> > > > > > >
> >> > > > > > > > Hey all,
> >> > > > > > > >
> >> > > > > > > > GitHub recently created a new repository "triage" role
> >> > > > > > > > <
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization
> >> > > > > > > > >that
> >> > > > > > > > allows people to label and close PRs and issues, edit
> wikis
> >> and
> >> > > do
> >> > > > a
> >> > > > > > few
> >> > > > > > > > other things.
> >> > > > > > > >
> >> > > > > > > > I believe the ASF is now willing to grant that role to
> >> people
> >> > in
> >> > > > our
> >> > > > > > > > community without having to vote, we just need to open a
> >> Jira
> >> > > > ticket
> >> > > > > > with
> >> > > > > > > > Apache infra.
> >> > > > > > > >
> >> > > > > > > > So who wants in? Just reply with your GitHub handle and
> >> I'll be
> >> > > > happy
> >> > > > > > to
> >> > > > > > > > open a group ticket with everyone who's interested.
> >> > > > > > > >
> >> > > > > > > > Max
> >> > > > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > --
> >> > > > > > >
> >> > > > > > > *Rob DiCiuccio* (he/him)
> >> > > > > > > Director of Engineering
> >> > > > > > > Preset | https://preset.io
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > > >
> >> > > > > --
> >> > > > > Eugenia Moreno <https://www.linkedin.com/in/eugeniamorenozerdan
> >
> >> > > > > *Customer Engagement*
> >> > > > > *Preset.io* <http://preset.io/>
> >> > > > > Book Time with me <https://meetings.hubspot.com/eugenia5>
> >> > > > > C: 617-633-7641
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>

Re: GitHub "triage" role for PMs & active contributors

[Junlin Chen]

Zuzana(zuzana-vej) and I(JunlinC) volunteer to help cleanup the existing
labels and issues, and put together a labeling guideline for the community.
Thanks!

On Tue, Sep 15, 2020 at 10:51 AM Eugenia Moreno  wrote:

> eugeniamz please!
>
> On Tue, Sep 15, 2020 at 1:48 PM Srinivasa Kadamati 
> wrote:
>
> > Good call Max, I'm in (and I want to onboard the Champions next week
> too):
> > *srinify*
> >
> > On Tue, Sep 15, 2020 at 1:39 PM Rob DiCiuccio  wrote:
> >
> > > Yes please: robdiciuccio
> > >
> > > On Mon, Sep 14, 2020 at 9:27 PM Maxime Beauchemin <
> > > maximebeauche...@gmail.com> wrote:
> > >
> > > > Hey all,
> > > >
> > > > GitHub recently created a new repository "triage" role
> > > > <
> > > >
> > >
> >
> https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization
> > > > >that
> > > > allows people to label and close PRs and issues, edit wikis and do a
> > few
> > > > other things.
> > > >
> > > > I believe the ASF is now willing to grant that role to people in our
> > > > community without having to vote, we just need to open a Jira ticket
> > with
> > > > Apache infra.
> > > >
> > > > So who wants in? Just reply with your GitHub handle and I'll be happy
> > to
> > > > open a group ticket with everyone who's interested.
> > > >
> > > > Max
> > > >
> > >
> > >
> > > --
> > >
> > > *Rob DiCiuccio* (he/him)
> > > Director of Engineering
> > > Preset | https://preset.io
> > >
> >
>
>
> --
> Eugenia Moreno 
> *Customer Engagement*
> *Preset.io* 
> Book Time with me 
> C: 617-633-7641
>

Re: Podling Superset Report Reminder - September 2020

[Junlin Chen]

Dear mentors,

Quarterly report has been submitted. Please let us know if you have any 
questions. Thank you! 
https://cwiki.apache.org/confluence/display/INCUBATOR/September2020#superset 


Best,
Junlin 



On 2020/08/27 01:55:52, jm...@apache.org wrote: 
> Dear podling,> 
> 
> This email was sent by an automated system on behalf of the Apache> 
> Incubator PMC. It is an initial reminder to give you plenty of time to> 
> prepare your quarterly board report.> 
> 
> The board meeting is scheduled for Wed, 16 September 2020.> 
> The report for your podling will form a part of the Incubator PMC> 
> report. The Incubator PMC requires your report to be submitted 2 weeks> 
> before the board meeting, to allow sufficient time for review and> 
> submission (Wed, September 02).> 
> 
> Please submit your report with sufficient time to allow the Incubator> 
> PMC, and subsequently board members to review and digest. Again, the> 
> very latest you should submit your report is 2 weeks prior to the board> 
> meeting.> 
> 
> Candidate names should not be made public before people are actually> 
> elected, so please do not include the names of potential committers or> 
> PPMC members in your report.> 
> 
> Thanks,> 
> 
> The Apache Incubator PMC> 
> 
> Submitting your Report> 
> 
> --> 
> 
> Your report should contain the following:> 
> 
> *   Your project name> 
> *   A brief description of your project, which assumes no knowledge of> 
> the project or necessarily of its field> 
> *   A list of the three most important issues to address in the move> 
> towards graduation.> 
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be> 
> aware of> 
> *   How has the community developed since the last report> 
> *   How has the project developed since the last report.> 
> *   How does the podling rate their own maturity.> 
> 
> This should be appended to the Incubator Wiki page at:> 
> 
> https://cwiki.apache.org/confluence/display/INCUBATOR/September2020> 
> 
> Note: This is manually populated. You may need to wait a little before> 
> this page is created from a template.> 
> 
> Note: The format of the report has changed to use markdown.> 
> 
> Mentors> 
> ---> 
> 
> Mentors should review reports for their project(s) and sign them off on> 
> the Incubator wiki page. Signing off reports shows that you are> 
> following the project - projects that are not signed may raise alarms> 
> for the Incubator PMC.> 
> 
> Incubator PMC> 
> 

User Feedback for Superset Global Navigation

[Junlin Chen]

Hi all,

Preset is planning to conduct a series of User Interviews/Surveys to
collect user feedback for Superset Global Navigation. (Global
Navigation Also called: main navigation, primary navigation, main nav. )
Global navigation represents the top-level pages of a site’s structure—or
the pages below the home page. Optimized global navigation in Superset will
support a variety of user tasks and modes of information seeking, including
known-item seeking, exploration, and even re-finding.The goal of this User
Interview is to understand better how users currently navigate and find
content in Superset. At a high level, we want to understand what users are
trying to accomplish, how they do this, and what could be improved.We would
like to work with voluntary users for a 20-30 minute session next week.
Please let us know if you are interested. If you are in Slack, please join
#user-interviews .
Thank you!!

Best,
Junlin

Re: Giving our PMs and contributors triage rights on GitHub

[Junlin Chen]

humbly asking +1. Currently, we PMs at Preset are tracking Github issues
Projects, Milestone and Link PR manually which is extremely inefficient. By
doing so, we are not able to provide status updates timely to
the community.



On Thu, Aug 13, 2020 at 3:52 PM Evan Rusackas  wrote:

> An emphatic +1 from me! The issues could gain a huge boost from the added
> human curation, whether it's adding sensible labels, running Project kanban
> boards, linking issues to PRs (and other relevant issues), and more. It
> could not only bring some order to the chaos, but help those in the
> community reporting issues feel like they’re being heard.
>
> Evan Rusackas
> ( he | him )
> Frontend Lead
> Preset | preset.io
> On Aug 13, 2020, 9:28 AM -0700, Maxime Beauchemin <
> maximebeauche...@gmail.com>, wrote:
> > Hi all,
> >
> > It just came to my attention that GitHub added a new "triage" access
> level
> > at the repo level.
> > https://github.blog/changelog/2019-05-23-triage-and-maintain-roles-beta/
> >
> > In the past, we've identified that it was impossible for non-committers
> > (especially our PMs and contributors-that-are-not-yet-committers) to help
> > us triage issues, apply labels, assign reviews, close and reopen issues
> as
> > needed. It's really clear to me that we really need all the help we can
> get
> > in this area, and that not being able to involve more people into this
> > process hurts us, and is a clear operational downside of using the ASF
> > infra.
> >
> > I'd like to build a case for this to become allowed by ASF infra. But
> > first, I'd love to see some +1s, and a list of GitHub handles for people
> in
> > our community who could make use of this feature.
> >
> > More technically, I think the way to make that easy and painless would be
> > to add a new entry to the `.asf.yaml` file that would enable maintainers
> to
> > assign the "triage" role to whoever they see fit. For reference, here's
> > more context on that piece of automation I'd like to latch this onto
> here:
> >
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features
> >
> > FYI, xposting this to general@incubator for their attention.
> >
> > Max
>

Re: Graduation

[Junlin Chen]

Community and @mentors,

We've been working on graduation, and going through our status file and
checklist
.
Please chime in and help complete it if you have the information.
Superset website and WIKI are being updated, following the Podling Website
Requirements.

Mentors, there are mentor related items that need to be confirmed, please
help check below.

   - You have subscribed to the pmc and general lists.
   - You have access to the incubator repository
   - You have been tracking project progress.

We also noticed that some of the links on the graduation page
 are broken and would
like to bring it to your attention.

Thanks for your support!

Best,
Junlin

On Thu, Jul 30, 2020 at 4:21 PM Maxime Beauchemin  wrote:

> Community and @mentors!
>
> Junlin and I were talking about pushing the graduation process forward,
> and even though I've done it once before, we could really use some help
> around navigating the process.
>
> The first step is to look at the checklist and identify the gaps, and I
> think there are very few at this time.
>
> Can one of our mentors volunteer to provide guidance?
>
> Volunteers are welcomed as always, we'll also communicate as we break down
> the checklist into tasks.
>
> Thanks,
>
> Max
>