Re: [ANNOUNCE] Please welcome new Superset committer Erik Ritter
Congrats Erik!! On Thu, Aug 29, 2019 at 10:11 AM Eli Brumbaugh wrote: > Congratulations Erik! 🙌 > > On Thu, Aug 29, 2019 at 10:03 AM Ville Brofeldt < > ville.v.brofe...@gmail.com> > wrote: > > > Congratulations Erik, well deserved and definitely an asset to the > project! > > Ville > > > > On Thu, Aug 29, 2019, 19:49 Grace Guo > > wrote: > > > > > Hi folks! > > >I'm very pleased to announce that the Superset PMC has voted Erik > > > Ritter to be a committer. Since late May this year, he has closed a few > > > pull requests ( > > > > > > https://github.com/apache/incubator-superset/pulls?q=is%3Apr+author%3Aetr2460+is%3Aclosed > > > < > > > > > > https://github.com/apache/incubator-superset/pulls?q=is:pr+author:etr2460+is:closed > > >), > > > covering bug fixes, chores, new features. Erik has done incredible work > > in > > > improving Superset’s documentation, issues and community involvement. > > > > > > Please join me in welcoming Erik Ritter! > > > > > > Thanks, > > > > > > Grace > > > on behalf of the Superset PMC > > > > > > > > > -- > Eli Sebastian Brumbaugh > Pronouns: He, Him, His > Design Manager | Data Platform, Production Platform, Information Security > Indigenous@ Airfinity Group Founder >
Re: [VOTE] SIP-15/15A Proposal for Transparent and Consistent Time Intervals
+1 On Wed, Jun 19, 2019 at 2:42 PM John Bodley wrote: > Hi, > > I would like to call a vote on SIP-15/15A: > >- https://github.com/apache/incubator-superset/issues/6360 >- https://github.com/apache/incubator-superset/issues/7656 > > These are proposals for transparent and consistent time intervals across > the Druid REST API and SQLAlchemy connectors. Note though the logic is > quite simple the changes required are somewhat involved and include a > method for transitioning between the current and proposed solutions. > > If anyone has any hesitation, questions, or concerns about the logic please > comment on the relevant SIPs. > > Thanks > -John >
Re: [VOTE] Hosting questions / answers on StackOverFlow
+1 On Tue, Apr 23, 2019 at 5:42 PM Krist Wongsuphasawat wrote: > Hi Superset Community, > > Per the previous thread "[DISCUSS] Best place for questions / answers", > there is a proposal to > >- Host Superset Q&A (questions such as "How do I do something in >Superset?") on StackOverFlow instead of github issues. >- New questions on other channels (github/slack/etc.) will not be >answered and the authors will be notified to ask on StackOverFlow > instead. >- Only keep bug reports, feature requests and project maintenance issues >on github. Old FAQs can be copied over to StackOverFlow. (Will need >volunteers for this.) > > I would like to call for a VOTE to migrate to StackOverFlow. > Please +1 if you support this decision, 0 for no comment or -1 if you > disagree. > > This poll will end on Friday April 26th, 11:59pm Pacific time. > > Best regards, > > Krist > > -- > > *Krist Wongsuphasawat* > http://kristw.yellowpigz.com >
Re: The state of releases
To answer the question about using a workflow for managing releases/branches/tags, I previously evaluated using conventional commits: https://www.conventionalcommits.org/en/v1.0.0-beta.3/, which is a system for tagging commits to generate the changelog. At the time it seemed like it may have issues creating the Changelog with the way we commit everything to master then cherry-pick fixes onto a branch, but the consistency in tagging PRs with fix, feature, docs seemed useful. I don't think we've heavily discussed other workflows. Sounds good to get suggestions for improvement on SIP-12. On Tue, Mar 19, 2019 at 9:27 PM David Smith wrote: > I'm new to this project, so I apologize if this has been discussed > previously, but... Have we considered using a widely adopted workflow for > managing releases/branches/tags, and using tools that the community has > already built for them? For example Git Flow or some variant thereof? For > anyone who is unfamiliar, see overview and tooling--in the form of git > extensions--here: https://github.com/nvie/gitflow > > I saw SIP-12 and have a few comments that I will try to document tomorrow > on that issue, but I'm really curious whether other common processes/flows > were rejected explicitly or if they just didn't come up? > > Dave > > > > On Tue, Mar 19, 2019 at 8:45 PM Maxime Beauchemin < > maximebeauche...@gmail.com> wrote: > > > Wondering what to do next, Justin, is it ok for me to push the related > tag > > to Github? > > > > Should I trigger a [VOTE] thread? > > > > Max > > > > On Tue, Mar 19, 2019 at 12:04 AM Maxime Beauchemin < > > maximebeauche...@gmail.com> wrote: > > > > > My svn is a bit rusty but I made some progress tonight: > > > https://github.com/apache/incubator-superset/pull/7054 > > > > > > Pushed some files to SVN > > > https://dist.apache.org/repos/dist/dev/incubator/superset/0.31.0rc18/ > > > > > > It's not intended to be an actual real RC, but it's a start. > > > > > > An early question is around RC numbers. Lyft & Airbnb have been doing a > > > lot of back and forth on the release branch already and `0.31.0` is > > already > > > up to rc18. I was internally debating what to do here, keeping the > > > numbering scheme, or starting anew. Probably the right thing to do is > to > > > pick a number (say 0.32.0) and start clean at 0.32.0rc1, and stick to > the > > > Apache process, and use continuous numbers. I'm assuming the handoff is > > at > > > 0.31.0rc18. > > > > > > Now people that would want to work on non-Apache release branches would > > do > > > so in their fork, and in their own namespace. Maybe their local build > > > instructions can become recipes for an upcoming release, but I suggest > > that > > > this happens in forks from now on. > > > > > > Clearly this Apache process here with signing + svn commit + voting is > > > more involved than the usual git cherry-pick + git tag + git push, so > > that > > > should probably lead to less RCs (I can't imagine doing 18 votes > around a > > > single release). > > > > > > Not to mention the fact that the real complexity around releasing is > > > raising and labeling issues with a proper target version, gather PRs, > > > cherry-pick fixes and resolve conflicts if any. I'm hoping we can build > > > tooling to help with all this. Hugh started something a while back, but > > > there's lots to be done still in that area. > > > > > > Max > > > > > > On Mon, Mar 18, 2019 at 11:39 PM Maxime Beauchemin < > > > maximebeauche...@gmail.com> wrote: > > > > > >> Not officially approved yet, I think we should start a [DISCUSS] > thread > > >> and eventually [VOTE] > > >> > > >> On Mon, Mar 18, 2019 at 10:13 PM David Smith > > >> wrote: > > >> > > >>> Thanks Max! Out of curiosity, has that release SIP-12 been approved > > yet? > > >>> I > > >>> have some thoughts but if it is already a done deal I'll wait until > > >>> another > > >>> time. :-) > > >>> > > >>> On Mon, Mar 18, 2019 at 9:53 PM Maxime Beauchemin < > > >>> maximebeauche...@gmail.com> wrote: > > >>> > > >>> > Hi all, > > >>> > > > >>> > I wanted to send an email explaining the current state of releases > > and > > >>> > start a thread about what's ahead. > > >>> > > > >>> > Early on in the project lifecycle, I used to package releases and > > push > > >>> to > > >>> > Pypi without much process. I'd package internal releases internally > > for > > >>> > Airbnb. We'd roll out to staging, stabilize the release, and launch > > in > > >>> > production. After a some time without major issues and regressions, > > I'd > > >>> > push a new release out to Pypi and make it available to the > > community. > > >>> That > > >>> > process worked ok when I reviewed or wrote most PRs and had a > handle > > on > > >>> > everything that was going on. The community has grown much, and > > clearly > > >>> > that process has not been appropriate for quite some time now. > > >>> > > > >>> > Later on, we joined the Apache Software Foundation's incubator, and > > >>> the
Re: New Committer: Krist Wongsuphasawat
Congrats Krist!! On Tue, Nov 20, 2018 at 6:17 AM Stephanie Rivera wrote: > < > https://chrome.google.com/webstore/detail/bitmoji/bfgdeiadkckfbkeigkoncpdieiiefpig > > > Cheers, > > Stephanie > > > *Stephanie Rivera* |* Sr. Director of Data Intelligence* > > 8181 Arista Place | Suite 300 | Broomfield, CO 80021 | Westminster, CO > 80020 > < > http://www.google.com/url?q=http%3A%2F%2Fwww.spotxchange.com%2F&sa=D&sntz=1&usg=AFrqEzdlZjMtAvYRCQByfN6D_6PjZhSbSw > > > > < > https://www.google.com/url?q=https%3A%2F%2Fdl.dropbox.com%2Fs%2F5se5ucpqodjsq1h%2Flinkedin.png&sa=D&sntz=1&usg=AFrqEzdTHQrlDWywpW7VZVpwGJJdOBY-Wg > > > > > > > On Tue, Nov 20, 2018 at 12:47 AM Jeff Feng wrote: > > > The Project Management Committee (PMC) for Apache Superset has invited > > Krist Wongsuphasawat to become a committer and we are pleased to announce > > that he has accepted. > > > > Being a committer enables easier contribution to the project since there > is > > no need to go via the patch submission process. This should enable better > > productivity. Being a PMC member enables assistance with the management > and > > to guide the direction of the project. > > > > Congratulations Krist! > > Jeff > > >
Re: [SIP-0] Vote
+1 On Wed, Oct 24, 2018 at 2:54 PM Fabian Menges wrote: > +1 > > On Wed, Oct 24, 2018 at 5:38 PM Eli Brumbaugh > wrote: > > > +1 > > On Wed, Oct 24, 2018 at 2:37 PM Maxime Beauchemin < > > maximebeauche...@gmail.com> wrote: > > > > > FYI > > > https://community.apache.org/committers/voting.html > > > > > > On Wed, Oct 24, 2018 at 1:59 PM Beto Dealmeida > > > wrote: > > > > > > > Hi, all. > > > > > > > > I would like to call a vote on SIP-0, "Superset Improvement > Proposals": > > > > > > > > https://github.com/apache/incubator-superset/issues/5602 > > > > > > > > Beto > > > > > > > > > > > > > -- > > Eli Sebastian Brumbaugh > > Design Lead | Data Platform | Data UX > > Indigenous@ Diversity Group Founder > > >
