potiuk commented on PR #44494:
URL: https://github.com/apache/airflow/pull/44494#issuecomment-2509012064
Also technically speaking- when it comes to the mechanics of it.
That should be of course a bit of a burden for you and your team - but this
is completely no problem to fork Airflow and run `breeze
prepare-proivders-package edge` from it - update versions there, test it etc.
So this is just a matter of backporting any changes in `main` edge executor
to that fork to make it works with Airflow 2.10 / AIP-44.
You can also easily run the same compatibility tests ets in your CI -
starting from that fork, so technically speaking you could do everything to
release next "2.10" compatible edge worker on your own - without having to keep
the compatibility in Airflow repo.
So all that is doable - the question is - should it slow down the current
Airflow 3 development, or should it slow down Bosh's team runnning the 2.10
version of it. i think that's basiclly the choice we are facing now.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
