+1 On Thu, Nov 12, 2020 at 1:31 PM Evan Rusackas <[email protected]> wrote:
> +1! > > One suggestion here might be to add one or more new Issue Templates > to GitHub to handle the specific info/needs that pertain to the other > repos, and add appropriate labels. > > On a related, there has been some interest in consolidating parts of > superset-ui into incubator-superset as well. I’ve been threatening to write > a SIP about it, but have been holding off until we’re closer to having the > bandwidth to perform the actual work. In any case, this seems like a > related step. > > In my mind, the issues all fall under the Superset umbrella, and it would > seem useful to have a uniform triage/labelling process for these issues, so > I support it. > > Thanks, > > Evan Rusackas > ( he | him ) > Frontend Lead > Preset | preset.io > On Nov 9, 2020, 8:26 PM -0800, Maxime Beauchemin < > [email protected]>, wrote: > > +1 > > > > On Wed, Nov 4, 2020, 11:30 PM Junlin Chen <[email protected]> wrote: > > > > > 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 > > > > > > >
