Thanks Ash! The current place for logos is:
https://github.com/apache/airflow/tree/master/docs/img/logos. We should
find a nice home for logos in the new website too.
Would it be possible to get vector and high-res copies soon? The work on
the website has started and it would great to play with
Amazing! congrats and thank you.
On Tue, 27 Aug 2019 at 22:25, Jarek Potiuk wrote:
> Hello everyone,
>
> After a long time in the making I merged "Breeze" environment which is a
> swiss-knife of everything testing in Airflow. It should make it even easier
> to contribute to Airflow (easier to
Hello everyone,
After a long time in the making I merged "Breeze" environment which is a
swiss-knife of everything testing in Airflow. It should make it even easier
to contribute to Airflow (easier to test your changes locally while
development in general).
There is a fairly comprehensive
How about an alternative approach that would introduce 2 new keyword
arguments that are clear (something like, but maybe better than
`period_start_dttm`, `period_end_dttm`) and leave `execution_date`
unchanged, but plan it's deprecation. As a first step `execution_date`
would be inferred from the
Execution date is execution date for a dag run no matter what. There is no end
interval or start interval for a dag run. The only time this is relevant is
when we calculate the next or previous dagrun.
So I don't Daniels rationale makes sense (?)
Sent from my iPhone
> On 27 Aug 2019, at
I agree with Daniel's rationale but I am also worried about backwards
compatibility as this would perhaps be the most disruptive breaking change
possible. I think maybe we should write down the different options
available to us (AIP?) and call for a vote. What does everyone think?
On Tue, Aug 27,
Can't execution date can already mean different things depending on if the
dag run was initiated via the scheduler or manually via command line/API?
I agree that making it consistent might make it easier to explain to new
users, but should we exchange that for breaking pretty much every existing
I let this run for a little longer (mostly due to public holiday in the UK on
Monday and me having a little bit of well-deserved outside time!).
The result is as follows:
Option 1: 22 votes
Option 2: 7
Keep with current: 1 vote
So the winner is option 1. Vector and high-res copies will follow
Awesome, fingers crossed! :)
Cheers,
Szymon
On Tue, 27 Aug 2019 at 00:24, Kevin Yang wrote:
> Very excited, looking forward to it. Thank you guys
>
> Cheers,
> Kevin Y
>
> On Mon, Aug 26, 2019 at 10:04 AM Kamil BreguĊa
> wrote:
>
> > Hello,
> >
> > I am very happy to be able to work on this
