🎉🎉 Thank you Ash for cutting the release!
On Wed, Nov 21, 2018 at 6:09 PM Sid Anand wrote:
> Excellent work Ash! Thanks for doing the needful!!
>
> -s
>
> On Wed, Nov 21, 2018 at 5:40 PM Tao Feng wrote:
>
> > Thanks Ash for running the release!
> >
> > On Wed, Nov 21, 2018 at 2:20 PM Ash Berlin
Excellent work Ash! Thanks for doing the needful!!
-s
On Wed, Nov 21, 2018 at 5:40 PM Tao Feng wrote:
> Thanks Ash for running the release!
>
> On Wed, Nov 21, 2018 at 2:20 PM Ash Berlin-Taylor wrote:
>
> > Dear Airflow community,
> >
> > I'm happy to announce that Airflow 1.10.1 was just rele
Thanks Ash for running the release!
On Wed, Nov 21, 2018 at 2:20 PM Ash Berlin-Taylor wrote:
> Dear Airflow community,
>
> I'm happy to announce that Airflow 1.10.1 was just released.
>
> The source release as well as the binary "sdist" release are available
> here:
>
>
> https://dist.apache.org
🎉🎉 Great stuff Ash.
On Wed, Nov 21, 2018, 22:20 Ash Berlin-Taylor Dear Airflow community,
>
> I'm happy to announce that Airflow 1.10.1 was just released.
>
> The source release as well as the binary "sdist" release are available
> here:
>
>
> https://dist.apache.org/repos/dist/release/incubator/
Thanks Ash for running the release!
On Wed, Nov 21, 2018 at 2:17 PM Ash Berlin-Taylor wrote:
> The vote to release Airflow 1.10.1-incubating, having been open for 3
> days is now closed.
>
> There were three binding +1s and no -1 votes.
>
> +1 (binding):
> Hitesh Shah
> Jakob Homan
> Justin Mcle
Dear Airflow community,
I'm happy to announce that Airflow 1.10.1 was just released.
The source release as well as the binary "sdist" release are available here:
https://dist.apache.org/repos/dist/release/incubator/airflow/1.10.1-incubating/
We also made this version available on PyPi for c
The vote to release Airflow 1.10.1-incubating, having been open for 3
days is now closed.
There were three binding +1s and no -1 votes.
+1 (binding):
Hitesh Shah
Jakob Homan
Justin Mclean
The release is approved.
Thanks to all those who voted.
Cheers,
Ash
> On 21 Nov 2018, at 04:44, Justi
Hi,
I am not sure about that, there has to be a provision to stop multiple
builds same PR irrespective user's access to repo. I think admins have to
update settings of repo in travis.
[image: Screenshot 2018-11-21 at 10.46.11 PM.png]
On Wed, 21 Nov 2018 at 22:18, Deng Xiaodong wrote:
> Hi,
>
> I
An add-up: given you have the write access to your own fork, you would be able
to cancel/re-run the Travis CI jobs which are running against your own fork.
XD
> On 22 Nov 2018, at 12:48 AM, Deng Xiaodong wrote:
>
> Hi,
>
> I believe only the folks who have write access to the codebase, i.e. t
Hi,
I believe only the folks who have write access to the codebase, i.e. the
committers, can stop/cancel/re-run the Travis CI jobs.
What the contributors can do is to make commits to the branch in their own fork
& ensure it’s working/passing tests as expected, before they create the Pull
Reque
Deng Xiaodong thanks for helping us with this. I hope this will help us in
developing and testing fast. I would like to ask is there a provision to
cancel our own builds in travis. I can see sometimes contributors are
pushing multiple commits in small intervals of time leading to multiple
builds. I
Hi folks,
I noticed that testing is somehow a problem for some folks who would like
to contribute (either have trouble setting local testing env, or misused
Pull Request to test). Actually because Airflow is using Travis CI for unit
testing, running testing for any of your change/commit is very ve
12 matches
Mail list logo
