Thanks Rahul! (+1 binding) I have checked and verified below for both Apache Airflow 3.2.0rc2 and Task SDK 1.2.0rc2, - Reproducible package builds - SVN - Licence - Signature - Checksums
I tested a few example DAGs using Breeze with SAM (SimpleAuthManager with Admin). The basic verification and functionality checks look good. I did not have the opportunity to perform more in-depth testing. On Mon, Apr 6, 2026 at 8:04 PM Vikram Koka via dev <[email protected]> wrote: > Thanks Rahul. > > +1 binding on Airflow Core and TaskSDK. > > I tested the 3.2.0rc2 with some of the example DAGs and some of my DAGs > built with common.sql and an early version of common.ai. > I tested both with airflow standalone and with local executor. > > I ran into some issues, but Pavan determined that those were issues those > specific providers and not with Airflow core. > After a configuration change, based on his recommendation, my DAGs ran > fine. > > Vikram > > > > On Mon, Apr 6, 2026 at 9:18 AM Jens Scheffler <[email protected]> wrote: > > > Thanks for the RC2, Rahul! > > > > Airflow/Airflow Core: +1 (binding), checked: > > - SVN > > - Reproducible package build > > - Licenses > > - Signatures > > - Checksums > > - Install in Docker > > - Source tarball > > Task SDK: +1 (binding), checked: > > - SVN > > - Reproducible package build > > - Licenses > > - Signatures > > - Checksums > > - Install in Docker > > > > Note: This is a technical check (only) as of now. As of easter time I am > > in parallel not able to test all and everything. Basic checks are OK > > (testing plain vanilla setup via breeze with EdgeExecutor and > > Integration Test Dag). > > > > So I did not conclude testing and will further test in parallel, once I > > find real problems I'll post it here, until then I see it as working. > > > > On 06.04.26 09:03, Pankaj Koti via dev wrote: > > > Thanks Rahul. > > > > > > If it helps, just confirming that I received the email on Friday itself > > > 7:03 PM IST (my time) as a regular email (Not in the spam folder) > > > > > > On Mon, Apr 6, 2026 at 12:19 PM Rahul Vats <[email protected]> > > wrote: > > > > > >> Resending this for visibility, as it seems some recipients did not > > receive > > >> the original email, even though it was listed on the Apache mailing > > list. > > >> <https://lists.apache.org/thread/z4l33ydpqzbcxbhno3gm8yf99fswhsrz> > > >> > > >> Regards, > > >> Rahul Vats > > >> > > >> On Fri, 3 Apr 2026 at 19:02, Rahul Vats <[email protected]> > wrote: > > >> > > >>> Hey fellow Airflowers, > > >>> > > >>> The release candidates for Apache Airflow 3.2.0rc2 and Task SDK > > 1.2.0rc2 > > >>> are now available for testing! > > >>> > > >>> This email is calling for a vote on the release, which will last at > > least > > >>> until *07th Apr* and until 3 binding +1 votes have been received. > > >>> > > >>> Consider this my +1 binding vote. > > >>> > > >>> Airflow 3.2.0rc2 is available at: > > >>> https://dist.apache.org/repos/dist/dev/airflow/3.2.0rc2/ > > >>> > > >>> "apache-airflow" Meta package: > > >>> - *apache-airflow-3.2.0-source.tar.gz* is a source release that comes > > >> with > > >>> INSTALL instructions. > > >>> - *apache-airflow-3.2.0.tar.gz* is the binary Python "sdist" release. > > >>> - *apache_airflow-3.2.0-py3-none-any.whl* is the binary Python wheel > > >>> "binary" release. > > >>> > > >>> "apache-airflow-core" package: > > >>> - *apache_airflow_core-3.2.0.tar.gz* is the binary Python "sdist" > > >> release. > > >>> - *apache_airflow_core-3.2.0-py3-none-any.whl* is the binary Python > > wheel > > >>> "binary" release. > > >>> > > >>> Task SDK 1.2.0 is available at: > > >>> https://dist.apache.org/repos/dist/dev/airflow/task-sdk/1.2.0rc2/ > > >>> > > >>> "apache-airflow-task-sdk" package: > > >>> - *apache_airflow_task_sdk-1.2.0.tar.gz* is the binary Python "sdist" > > >>> release. > > >>> - *apache_airflow_task_sdk-1.2.0-py3-none-any.whl* is the binary > Python > > >>> wheel "binary" release. > > >>> > > >>> Public keys are available at: > > >>> https://dist.apache.org/repos/dist/release/airflow/KEYS > > >>> > > >>> Please vote accordingly: > > >>> > > >>> [ ] +1 approve > > >>> [ ] +0 no opinion > > >>> [ ] -1 disapprove with the reason > > >>> > > >>> Only votes from PMC members are binding, but all members of the > > community > > >>> are encouraged to test the release and vote with "(non-binding)". > > >>> > > >>> The test procedure for PMC members is described in: > > >>> > > >>> > > >> > > > https://github.com/apache/airflow/blob/main/dev/README_RELEASE_AIRFLOW.md\#verify-the-release-candidate-by-pmc-members > > >>> The test procedure for contributors and members of the community who > > >> would > > >>> like to test this RC is described in: > > >>> > > >>> > > >> > > > https://github.com/apache/airflow/blob/main/dev/README_RELEASE_AIRFLOW.md\#verify-the-release-candidate-by-contributors > > >>> Please note that the version number excludes the 'rcX' string, so > it's > > >> now > > >>> simply 3.2.0 for Airflow package and 1.2.0 for Task SDK. This will > > allow > > >>> us > > >>> to rename the artifact without modifying > > >>> the artifact checksums when we actually release. > > >>> > > >>> Docs (for preview): > > >>> https://airflow.staged.apache.org/docs/apache-airflow/3.2.0 > > >>> > > >>> Release Notes: > > >>> - https://github.com/apache/airflow/blob/3.2.0rc2/RELEASE_NOTES.rst > > >>> - https://airflow.staged.apache.org/docs/apache-airflow/3.2 > > >>> .0/release_notes.html > > >>> (Rendered HTML) > > >>> > > >>> Testing Instructions using PyPI: > > >>> You can build a virtualenv that installs this and other required > > packages > > >>> (e.g. task sdk), like this: > > >>> > > >>> uv venv > > >>> uv pip install -U \ > > >>> apache-airflow==3.2.0rc2 \ > > >>> apache-airflow-core==3.2.0rc2 \ > > >>> apache-airflow-task-sdk==1.2.0rc2 > > >>> > > >>> Constraints files are at > > >>> https://github.com/apache/airflow/tree/constraints-3.2.0rc2 > > >>> > > >>> Regards, > > >>> Rahul Vats > > >>> > > >>> > > >>> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
