Re: [DISCUSSION] Proposal to Add Couchbase Provider to Apache Airflow

2025-05-15 Thread Shyam Rajamannar
Hi Jarek, Vikram, and the Airflow community, Thank you for the thoughtful feedback and valuable discussion. We understand and respect the perspective shared regarding maintaining the Couchbase provider outside the main Airflow repository—it makes sense, and we appreciate the clarity. However,

Re: [DISCUSSION] Proposal to Add Couchbase Provider to Apache Airflow

2025-05-15 Thread Jarek Potiuk
Sure you can improve visibility there, but also you have to be mindful that we (the Apache Airflow PMC) are not allowed to endorse or promote any non-community managed stuff - 3rd-party code etc. on our website. The website, release process, management, decision making and responsibility (and the l

[ANNOUNCE] Staging system for docs - including latest Provider wave

2025-05-15 Thread Jarek Potiuk
For those who are still going to take a look, at providers I just completed some testing and fixes and merged a few PRs of mine (few are still left) - and run some syncing - and can now say officially that this release of providers is the first one that uses our brand-new staging system for documen

Re: [ANNOUNCE] Staging system for docs - including latest Provider wave

2025-05-15 Thread Kaxil Naik
🎉 Woho On Fri, 16 May 2025 at 11:39, Jarek Potiuk wrote: > For those who are still going to take a look, at providers I just completed > some testing and fixes and merged a few PRs of mine (few are still left) - > and run some syncing - and can now say officially that this release of > providers

Re: [ANNOUNCE] Staging system for docs - including latest Provider wave

2025-05-15 Thread Pavankumar Gopidesu
Wooho, Thank you Jarek. This is really helpful to test docs and iterate changes. Regards, Pavan On Fri, May 16, 2025 at 7:09 AM Jarek Potiuk wrote: > For those who are still going to take a look, at providers I just completed > some testing and fixes and merged a few PRs of mine (few are still

Re: [DISCUSSION] Support policy for Airflow 2.x after the Airflow 3.0.0 release

2025-05-15 Thread Jed Cunningham
+1 to 6+6. Not sure we really need to clarify what the dates mean as part of setting timelines - we already operate this way. But if we have anywhere that is vague in our docs etc, of course being more explicit in those places makes sense.

Re: [VOTE] Airflow Providers prepared on May 14, 2025

2025-05-15 Thread Jarek Potiuk
+1 (binding) for everything except cncf.kubernetes (-1 for cncf.kubernetes). Tested Reproducibility, Checksums, Signatures, Licences, my changes, Installed all the packages. The cncf.kubernetes (also the last released 10.4.3) has a bug that prevent it from running on Airflow 2 (I introduced it by

Re: [VOTE] Airflow Providers prepared on May 14, 2025

2025-05-15 Thread Jens Scheffler
+1 (binding) - Checked SVN, Check in Docker, Reproducible package build, Licenses, Signatures Agree with Jarek's -1 opinion for cncf.kubernetes I explicitly tested the changes in Edge3 with our deployment in Bosch as well as I did a local breeze setup in Airflow 2.10.5 and current main - all

[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