I’m not too worried about that. I think people would learn pretty quickly. It
hasn’t been an issue for the kubernetes community so I can’t imagine it being
an issue for us. End-of-day, we only have a limited amount of compute power and
this will increase the speed we merge the PR’s that have pas
I tried this out today and I am absolutely in love. It certainly needs some
work (i.e. making it work for pull requests as well, faster updates, etc.) but
this 100x better than the GitHub system right now. I also think that since it
is open source, any airflow user who wants to start helping wit
I don't know if everyone has had experience managing a project of a similar
scale. Even if they did, I think the experience and knowledge of other
projects would still be helpful for us. Nobody knows everything.
I agree that community is more important than code, but that doesn't mean
we have to d
I think I can agree. Especially with flaky tests, some contributors may be
confused that some of the tests don't work on CI but work locally...
Checking the code quality is good first step. Once there's a review we can
start tests on CI.
On the other hand, I can see people asking for starting the
Hello all,
With the recent uptick in airflow contribution and pull requests, I have a
proposal that I hope will ensure that we do not find ourselves in a CI
backlog hell. I noticed that on the Kubernetes project, pull requests do
not run integration test until a committer submits a "ready to te
Just an update from my side regarding planning: I had some planning
meeting for the work for the next week and the only thing I will be able to
do (I plan it for tomorrow) is to release backport packages.
* Release a 2nd wave of Backport packages #10014
https://github.com/apache/airflow/issues/10
