Re: [Discuss] Airflow Summits 2020

How about "*Airflow Draught*" (sorry Breeze is already taken): >From https://www.lexico.com/en/definition/draught: A current of cool air in a room or other confined space. On Tue, Nov 19, 2019 at 8:25 PM Aizhamal Nurmamat kyzy wrote: > One more thing: > > Does anyone have a more interesting id

Re: Closing JIRA Issue for Merged PRs

+1 for probot. How about we try it with https://github.com/cchantep/probot-jira for example? On Tue, Nov 19, 2019 at 8:28 PM Daniel Imberman wrote: > +1 for probot, the k8s community has a pretty slick GitHub automation > system as well we should look into. > > via Newton Mail [ > https://cloudm

Re: Closing JIRA Issue for Merged PRs

+1 for probot, the k8s community has a pretty slick GitHub automation system as well we should look into. via Newton Mail [https://cloudmagic.com/k/d/mailapp?ct=dx&cv=10.0.32&pv=10.14.5&source=email_footer_2] On Tue, Nov 19, 2019 at 2:09 PM, Maxime Beauchemin wrote: Quick note as I'm playing w

Re: [Discuss] Airflow Summits 2020

One more thing: Does anyone have a more interesting idea on how to name our summits without calling them summits? Like they do with Tensorflow World, Flink Forward.. We don't need to spend much time thinking about it, if we can't come up with anything. Just a thought. On Tue, Nov 19, 2019 at 12:

Re: Closing JIRA Issue for Merged PRs

Quick note as I'm playing with Probot for Superset. It's possible to catch all sorts of Github event and trigger all sorts of side effects with it. On the Superset side we're looking to enable automation around Github comments and labeling. It's also offers potential around enabling people (PMs, c

Re: Closing JIRA Issue for Merged PRs

Thanks, Imran for pointing out to the script you guys use, we will surely have a look. On Tue, Nov 19, 2019 at 2:10 PM Imran Rashid wrote: > Hi, > > I'm mostly just a lurker here but I thought I'd point out the scripts we > use for spark: > > https://github.com/apache/spark/blob/master/dev/mer

Re: Closing JIRA Issue for Merged PRs

I am all for automation too. For now, I think the priority to build that is low. Once we have all the items in the Roadmap close to being done, we can surely get this kind of CLI built. Regards, Kaxil On Mon, Nov 18, 2019 at 10:14 PM Jarek Potiuk wrote: > Agree that Github issue are nicely inte

Re: Closing JIRA Issue for Merged PRs

Yes we do close JIRA issues that are not relevant or the problem mentioned is already fixed by other issue On Mon, Nov 18, 2019 at 9:12 PM Sergio Kef wrote: > On a slightly irrelevant note, do we ever close tickets as non-reproducable > or will-not-fix? > Last time I was going through open ticke

Re: Closing JIRA Issue for Merged PRs

Hi, I'm mostly just a lurker here but I thought I'd point out the scripts we use for spark: https://github.com/apache/spark/blob/master/dev/merge_spark_pr.py It makes it easy to standardize format of commit msgs, merge to multiple branches, and update jira. Every once in a while, somebody has t

Re: Closing JIRA Issue for Merged PRs

https://github.com/go-jira/jira with some careful scripting would go some way to doing this. There are also a few scripts in the dev/ folder of the repo. An example of a command I used in the last release: jira list -t list-fix -q "Key IN ($(git log --oneli

Re: [VOTE] Accept new Airflow website contribution

The website is great and will be even better when the full copy is ready. I really appreciate the work you;ve done guys! So from me it's +1 (non-binding). Bests, Tomek On Sat, Nov 16, 2019 at 12:10 AM Kaxil Naik wrote: > Sent on Slack > > On Fri, Nov 15, 2019 at 10:45 PM Kamil Breguła > wrote:

Re: [Discuss] Airflow Summits 2020

Read through the document today and it didn't have comments, overall LGTM On Mon, Nov 18, 2019 at 1:06 PM Sergio Kef wrote: > Great initiative, I am in Berlin and happy to help. > > S. > > On Mon, 18 Nov 2019 at 20:43, Aizhamal Nurmamat kyzy > wrote: > >> Hi Jarek, >> >> It will be great to hav