This is a great idea (both - Hacktoberfest and Pycon DE). I actually got my
Hacktoberfest T-shirt last year by contributing to Airflow :).
We will need to enable Github Issues in the project if we should follow
that (this is not technically needed but then people won't find the issues
through the
I think that will lead to a very large number of questions about why it worked
before and now it doesn’t when doing a clean install.
And additionally, if developing in a new install and deploying to an old
install, you would get different behavior. Adding to more confusion.
James Coder
> On S
I'm wondering if there is some way we can do this so that new installs will
pick up the new default, but anyone that carries over an Airflow.cfg from an
old install will keep their existing behaviour.
And then also is that a good/helpful idea or will that be more confusing than
not?
-a
> On 2
I definitely agree. If we don't update it in 2.0 it is going to be hard to
change that in any 2.x versions
On Thu, Sep 26, 2019 at 10:51 AM James Meickle
wrote:
> I am *strongly* in favor of using the 2.0 update to break compat here,
> because this is a very confusing feature to most new users o
I am *strongly* in favor of using the 2.0 update to break compat here,
because this is a very confusing feature to most new users of Airflow, but
also will break a _lot_ of DAGs. I feel like if we don't change this in 2.0
we probably won't for any 2.x either, which would be a shame.
On Wed, Sep 25
