There had been a discussion around this earlier, though I couldn't find the
thread. So if we want to release clients with each Airflow release, then
we've to move away from current semantic versioning, something which we had
decided in that thread.
Also, so far I've not seen any API changes in a
Hey all,
I have just cut the new wave Airflow Providers packages. This email is
calling a vote on the release,
which will last for 72 hours - which means that it will end on Friday,
November 18, 2022 2 am CET.
Consider this my (binding) +1.
This is a special release as all providers are only
Description:
In Apache Airflow versions prior to 2.4.3, there was an open redirect in the
webserver's `/login` endpoint.
Credit:
The Apache Airflow PMC would like to thank Bugra Eskici for reporting this
issue.
References:
https://github.com/apache/airflow/pull/27576
+1 on adding it to the release process.
There is even a very good reason for it, which will become all but mandatory.
In the future, when we implement Internal API AIP (AIP-44) - if the
user will want to use some airflow feature, they should be able to use
the Python API client to communicate
I think it makes sense and I'm a +1.
For the convenience of other readers I'll paste your rationale here:
The rationale i have - that from the point of view of provider, it's just a
> dependency change (which we generally consided non-breaking) and it does
> not break people's workflows in
Love the "Atmosphere" name :) +1
On Mon, Nov 14, 2022 at 9:09 PM Mehta, Shubham
wrote:
> +1 (non-binding) to the “Atmosphere: The Airflow Monthly”
>
>
>
> Other suggestion - “Symphony: The Airflow Monthly”
> Context – In one of the talks Jarek compared Airflow to orchestra who
> guides tasks
+1 (non-binding) to the “Atmosphere: The Airflow Monthly”
Other suggestion - “Symphony: The Airflow Monthly”
Context – In one of the talks Jarek compared Airflow to orchestra who guides
tasks for execution and that analogy stuck with me. I started looking into best
orchestra, and “Symphony” is
Hi all,
Hope you are doing well.
Bringing this to your attention to discuss the release process of airflow
api clients. (Go and Python):
- https://github.com/apache/airflow-client-python
- https://github.com/apache/airflow-client-go
At the moment clients versions are not synced with airflow
> On Nov 14, 2022, at 2:15 PM, Abhishek Bhakat
> wrote:
>
> I would like to suggest “Atmosphere”. This came to my mind when I think about
> Airflow in Clouds. Even different layers of Atmosphere have cool names.
I really like this! The full name could be “Atmosphere: The Airflow Monthly”.
Hi All,
I would like to suggest “Atmosphere”. This came to my mind when I think
about Airflow in Clouds. Even different layers of Atmosphere have cool
names.
Maybe it’s a lame suggestion.
Thanks,
Abhishek
On 15-Nov-2022 at 12:30:00 AM, John Thomas
wrote:
> Hi All,
>
> I'm looking to add a bit
Hi All,
I'm looking to add a bit more character to the newsletter by choosing a
name, and then updating the design and layout to match. Currently I'm
looking at three possible names, but I'm open to suggestions. Chime in if
you have opinions or ideas, and if I don't hear from anyone I'll use my
I hope to have the RC release for the November wave of providers
todays (pending https://github.com/apache/airflow/pull/27613 approval)
and unless someone has a problem with treating the min-version bump
approach as problematic, I would proceed assuming tha the lazy
consensus passed.
On Fri, Nov
Hey everyone,
I also reviewed ALL outstanding PRs and merged a few more that I think
were needed.
This release will have a few more "major" version upgrades. This is
the full list of "major" providers upgraded:
* apache.pig
* apache.pinot
* apache.spark
* asana
* cncf.kubernetes
*
Dear Airflow community,
I'm happy to announce that Airflow 2.4.3 was just released.
The released sources and packages can be downloaded via
https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-sources.html
Other installation methods are described in
Hello,
Apache Airflow 2.4.3 (based on RC1) has been accepted.
3 "+1" binding votes received:
- Ephraim Anierobi
- Jarek Potiuk
- Jed Cunningham
Vote thread:
https://lists.apache.org/thread/rkz55y0c4z7k8ttd9zwplz66vblzh78m
I'll continue with the release process, and the release announcement
15 matches
Mail list logo
