Hi,
To move things along even faster, instead of creating new packages, you can
even tell people to
put something like this in a requirements.txt file:
git+
https://github.com/apache/incubator-airflow@v1-10-test#egg=apache-airflow[celery,crypto,emr,hive,hdfs,ldap,mysql,postgres,redis,slack,s3]
Yes it does make sense. I will try to help out in testing.
On 15/06/2018, 18:01, "Bolke de Bruin" wrote:
Ok to kick this a bit forward. I can spend 1 hour every day coming week to
get 1.10 out. This means I will rebranch 1.10 from master coming Monday. Every
day until Friday I will make
Ok to kick this a bit forward. I can spend 1 hour every day coming week to get
1.10 out. This means I will rebranch 1.10 from master coming Monday. Every day
until Friday I will make a new package (not a release) that says please test
this and report issues. Friday I will kick off a vote for
Hi,
I have a sandbox cluster at work (3 EC2 VMs + Celery on Elasticache) that I
have been running 1.10 on. This is because we want to test in advance the
Kubernetes operator and RBAC. Happy to lend some assistance with that.
-James M.
On Fri, Jun 15, 2018 at 6:28 AM, Driesprong, Fokko
wrote:
Hi all,
As you might know, I'm a consultant at GoDataDriven and I just changed to a
different project. At this project they are not using Airflow (yet), so for
me it is hard to test the RC's etc. I'm willing to help in the process, but
currently I'm struggling to find time for the project on the
