Yes count me in. ✋
> On 7 Dec 2018, at 6:54 pm, Sid Anand wrote:
>
> I met Gerard Curiel in Melbourne earlier today and we talked about starting
> an Airflow community / meetup in Australia (perhaps Melbourne to start
> with). As an informal survey, do respond if you are an Ozzie on this list!
>
In my opinion this searching for dags is not ideal.
We should be explicitly specifying the dags to load somewhere.
> On 25 Nov 2018, at 10:41 am, Kevin Yang wrote:
>
> I believe that is mostly because we want to skip parsing/loading .py files
> that doesn't contain DAG defs to save time, as sc
+1 for putting the pre-releases on pypi, likely to get more testers this way.
> On 15 Nov 2018, at 4:37 am, Ash Berlin-Taylor wrote:
>
> We've had two regressions against this release reported in Slack so I'm
> cancelling this vote, to re-open a new one once these two PRs are merged:
>
> http
+1
Sent from my iPhone
> On 6 Sep 2018, at 12:45 pm, Sid Anand wrote:
>
> +1
>
> On Wed, Sep 5, 2018 at 7:38 PM Steve Carpenter
> wrote:
>
>> +1
>>
>>> On Wed, Sep 5, 2018 at 8:30 PM Sid Anand wrote:
>>>
>>> Hi Folks!
>>> In the Apache tradition, I'd like to ask the community to vote on
>
Can we please tag the final v1.10 commit?
I believe schedule_interval was deprecated as an Operator parameter.
From the code:
"schedule_interval is used for %s, though it has been deprecated as a task
parameter, you need to specify it as a DAG parameter instead",
> On 15 Aug 2018, at 06:30, Shubham Gupta wrote:
>
> Hi,
>
> In airfl
8 at 6:13 PM +0800, "刘松(Brain++组)"
> mailto:liuson...@megvii.com>> wrote:
>
> What is the magic to remove the task id ?
>
>
>
>
> On Wed, May 9, 2018 at 3:38 PM +0800, "Beau Barker"
> mailto:beauinmelbou...@gmail.com>> wrote:
>
>
Use xcom for communication between tasks.
In the upcoming version 1.10 there's no need to specify task_ids for xcom.
You can simply say:
self.xcom_pull(context, key='name')
> On 9 May 2018, at 17:22, Song Liu wrote:
>
> Hi,
>
> For the cross-task communication, there are two options:
> - xco
+1 for Github.
Also think that moving to Github issues would be a step in the right direction.
> On 11 Mar 2018, at 05:56, Matthew Housley wrote:
>
> +1 (binding)
>
> For future reference, is this vote for anyone on the mailing list, or for
> those with some kind of status in the project? I f
