[RESULT][VOTE] Release Airflow 2.11.0 from 2.11.0rc1

2025-05-20 Thread Kaxil Naik
Hello Airflow Community, The vote to release Apache Airflow version 2.11.0 based on 2.11.0rc1 is now closed. The vote PASSED with 4 binding "+1", 7 non-binding "+1" and 0 "-1" votes: *"+1" Binding votes*: - Kaxil Naik - Jens Scheffler - Jed Cunningham - Ephraim Anierobi *"+1" non-Binding votes

Re: [VOTE] Release Airflow 2.11.0 from 2.11.0rc1

2025-05-20 Thread Ephraim Anierobi
Re: [VOTE] Release Airflow 2.11.0 from 2.11.0rc1 > > +1 (binding) Checked reproducibility, signatures, checksums, licences. Used > it with the helm chart with a few different configs. >

Re: [VOTE] Release Airflow 2.11.0 from 2.11.0rc1

2025-05-20 Thread kalyan reddy
+1 (non-binding) From: Jed Cunningham Sent: 20 May 2025 12:13 To: dev@airflow.apache.org Subject: Re: [VOTE] Release Airflow 2.11.0 from 2.11.0rc1 +1 (binding) Checked reproducibility, signatures, checksums, licences. Used it with the helm chart with a few

Re: [VOTE] Release Airflow 2.11.0 from 2.11.0rc1

2025-05-20 Thread Buğra Öztürk
+1 (non-binding) On Tue, 20 May 2025, 08:43 Jed Cunningham, wrote: > +1 (binding) Checked reproducibility, signatures, checksums, licences. Used > it with the helm chart with a few different configs. >

Re: [VOTE] Release Airflow 2.11.0 from 2.11.0rc1

2025-05-19 Thread Jed Cunningham
+1 (binding) Checked reproducibility, signatures, checksums, licences. Used it with the helm chart with a few different configs.

Re: [VOTE] Release Airflow 2.11.0 from 2.11.0rc1

2025-05-19 Thread Rahul Vats
+1 (non-binding), verified running example DAGs all work fine. Regards, Rahul Vats On Mon, 19 May 2025 at 18:54, Wei Lee wrote: > Changing my vote to +1. Thanks > > Best, > Wei > > On Mon, May 19, 2025 at 8:38 PM Kaxil Naik wrote: > > > @weilee...@gmail.com : Since this is not a new bug > > a

Re: [VOTE] Release Airflow 2.11.0 from 2.11.0rc1

2025-05-19 Thread Wei Lee
Changing my vote to +1. Thanks Best, Wei On Mon, May 19, 2025 at 8:38 PM Kaxil Naik wrote: > @weilee...@gmail.com : Since this is not a new bug > and also localized to SQLite, could you reconsider changing your -1 to +1. > > On Mon, 19 May 2025 at 13:17, Amogh Desai > wrote: > >> +1 non bindi

Re: [VOTE] Release Airflow 2.11.0 from 2.11.0rc1

2025-05-19 Thread Kaxil Naik
@weilee...@gmail.com : Since this is not a new bug and also localized to SQLite, could you reconsider changing your -1 to +1. On Mon, 19 May 2025 at 13:17, Amogh Desai wrote: > +1 non binding. > > Ran a few example dags from my test suite, and performed a few clicks on > the > UI doing various

Re: [VOTE] Release Airflow 2.11.0 from 2.11.0rc1

2025-05-19 Thread Amogh Desai
+1 non binding. Ran a few example dags from my test suite, and performed a few clicks on the UI doing various things. (Using the old UI now seems hard!) Wei, your issue seems to be localised to SQLite. Thanks & Regards, Amogh Desai On Sun, May 18, 2025 at 2:34 PM Jens Scheffler wrote: > Hi

Re: [VOTE] Release Airflow 2.11.0 from 2.11.0rc1

2025-05-18 Thread Jens Scheffler
Hi Wei, mhm, checked the PR and somehow this is the wrong target branch. Migration from Airflow 2.2 were cut on main. If you want to fix something it would need to get to v2-11-test. Otherwise I kind of dis-agree on raising a -1 for a migration problem caused by a migration rule in 2.2.0 tha

Re: [VOTE] Release Airflow 2.11.0 from 2.11.0rc1

2025-05-18 Thread Wei Lee
I think so. Best, Wei > On May 18, 2025, at 2:41 PM, Rahul Vats wrote: > > Wei, the migration Issue is > only specific to SQLite, right? > > Regards, > Rahul Vats > > On Sun, 18 May 2025 at 11:41, Wei Lee wrote: > >> -1 (non-binding) >> >> Enc

Re: [VOTE] Release Airflow 2.11.0 from 2.11.0rc1

2025-05-17 Thread Rahul Vats
Wei, the migration Issue is only specific to SQLite, right? Regards, Rahul Vats On Sun, 18 May 2025 at 11:41, Wei Lee wrote: > -1 (non-binding) > > Encountered a few issues during testing `airflow db migrate` with 2.11.0rc1 > > Tried to put up fixe

Re: [VOTE] Release Airflow 2.11.0 from 2.11.0rc1

2025-05-17 Thread Wei Lee
-1 (non-binding) Encountered a few issues during testing `airflow db migrate` with 2.11.0rc1 Tried to put up fixes in https://github.com/apache/airflow/pull/50745 Best, Wei > On May 17, 2025, at 9:42 PM, Shahar Epstein wrote: > > +1 (non-binding) > > On Thu, May 15, 2025 at 10:53 PM Kaxil N

Re: [VOTE] Release Airflow 2.11.0 from 2.11.0rc1

2025-05-17 Thread Shahar Epstein
+1 (non-binding) On Thu, May 15, 2025 at 10:53 PM Kaxil Naik wrote: > Hey fellow Airflowers, > > The release candidates for *Apache Airflow 2.11.0rc1* are now available for > testing! > > This email is calling for a vote on the release, which will last at least > until 20th May, 6:00 am GMT and

Re: [VOTE] Release Airflow 2.11.0 from 2.11.0rc1

2025-05-16 Thread Vishnu Chilukoori
+1 non-binding -- Regards, Vishnu Chilukoori On Fri, May 16, 2025, 16:32 Jens Scheffler wrote: > +1 (binding) - Checked SVN, Reproducible package build, Licenses, > Signatures > > Tested 2.11.0rc1 also in our Bosch deployment and did a small load test > as regression. All looks good! > > On 15

Re: [VOTE] Release Airflow 2.11.0 from 2.11.0rc1

2025-05-16 Thread Jens Scheffler
+1 (binding) - Checked SVN, Reproducible package build, Licenses, Signatures Tested 2.11.0rc1 also in our Bosch deployment and did a small load test as regression. All looks good! On 15.05.25 21:52, Kaxil Naik wrote: Hey fellow Airflowers, The release candidates for *Apache Airflow 2.11.0rc1

Re: [VOTE] Release Airflow 2.11.0 from 2.11.0rc1

2025-05-16 Thread Jarek Potiuk
We have now https://airflow.staged.apache.org/docs/apache-airflow/2.11.0/index.html available -> docs for 2.11.0 . The nice thing is - I found already first issue with the docs thanks to this -> our drop-down for versions has 2.11.0 somewhere below 2.2.0 (alphabetic sorting) - so we should fix it

[VOTE] Release Airflow 2.11.0 from 2.11.0rc1

2025-05-15 Thread Kaxil Naik
Hey fellow Airflowers, The release candidates for *Apache Airflow 2.11.0rc1* are now available for testing! This email is calling for a vote on the release, which will last at least until 20th May, 6:00 am GMT and until 3 binding +1 votes have been received. Consider this my +1 binding vote. Ai