Re: [DISCUSSION] Assessing what is a breaking change for Airflow (SemVer context)

Happy to see the change I made was used as an example here ;-) Honestly the discussion is a bit long and getting increasingly general, so a bit hard to follow for me. But if I understand the conversation & issue correctly, here are my thoughts: - We may not want to make a strong statement like

Request for feedback on proposal for new OpenLineage provider in Airflow

Dear Airflow Community, I have been working on a proposal to bring an OpenLineage provider to Airflow . I am looking for feedback with the goal to post an official AIP. Please feel free to comment in the doc

Re: Amazon provider package system tests dashboard

This is really cool, thanks for setting all of this up! I just took a look at the dashboard and it is really helpful :) Le lun. 23 janv. 2023 à 16:55, Beck, Vincent a écrit : > The AWS Airflow team is happy to announce that the dashboard we have been > building which summarizes the health

Re: [DISCUSSION] Assessing what is a breaking change for Airflow (SemVer context)

I understand it's "convenient" if they want to extend k8s executor. But I guess my thought is, I'm not sure that convenience outweighs the competing good which is, freedom to develop k8s executor. I'm not saying don't extend k8s executor -- please do, and contribute it back. But for subclassing

[ANNOUNCE] Airflow Providers prepared on January 23, 2023 are ready

Dear Airflow community, I'm happy to announce that new versions of Airflow Providers packages were just released. https://pypi.org/project/apache-airflow-providers-apache-cassandra/3.1.1/ https://pypi.org/project/apache-airflow-providers-docker/3.5.0/

[RESULT][VOTE] Airflow Providers - release of January 23, 2023

Hello, Apache Airflow Providers (based on RC1) have been accepted. This release include the following providers: docker, apache.cassandra, papermill 3 "+1" binding votes received: - Elad Kalif (binding) - Jarek Potiuk (binding) - Jed Cunningham (binding) 1 "+1+ non-binding votes received: -

Re: [DISCUSSION] Assessing what is a breaking change for Airflow (SemVer context)

Yeah. The PR was mostly to bring things together- i.e to be able to say "this is really a public interface of ours". And by just doing it, I was actually hoping it will spark those kind of discussions where we will really detail on what it means for each of those to be public. Having it written