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] <https://github.com/rodrigc/incubator-airflow@master#egg=apache-airflow[celery,crypto,emr,hive,hdfs,ldap,mysql,postgres,redis,slack,s3]> and then "pip install -r requirements.txt". I found that to be an effective way to quickly test the branch and provide feedback without waiting for packages. -- Craig On Fri, Jun 15, 2018 at 10:01 AM Bolke de Bruin <[email protected]> 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 a new package (not a release) that says > please test this and report issues. Friday I will kick off a vote for > Release. > > Does that make sense? > > Cheers > Bolke > >
