+1 (binding) for both packages, I checked: - SVN - Licences - Signatures - Checksums
On Tue, Apr 21, 2026 at 9:42 PM Jens Scheffler <[email protected]> wrote: > Hi Rahul! > > Thanks for the fast re-release after fix! Did a quick check of DIFF > between rc2 and rc3 and tookt he accelerated check path. As on the > release ticket did a regression on Grid refresh, also made deployment to > production ready. PMC check gives: > > 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 > > Nevertheless we have seen some severe performance degradation in loading > the Grid in _some_ Dags. We were not able to triage down which condition > it was but it seems it was related especially to a Dag that had a mapped > task in a task group. No big complexity but we have seen that the URL > call > > https://airflow-api-server/ui/grid/runs/dag_name?limit=10&order_by=-run_after > sometimes took 20+ seconds. Will attempt the next days to see if our DB > is missing an index or how the query is constructed that makes in so > slow. But 90% of other checked Dags look good and we found only 1 Dag > that is really that slow, others respond in ~10 seconds on this URL. I > assume something got bad in that call compared to previous versions. (As > we skipped 3.2.0 not sure if it was already like this in 3.2.0 and was > not able to make a regression there) > > So besides the PMC voting of +1 (binding) I might need to lower it to > +0.9 (binding) - assuming sufficient other votes make it across the bar > but wanted to raise awareness of this. > > Jens > > On 21.04.26 20:13, Buğra Öztürk wrote: > > +1 (binding) for both Apache Airflow and Task SDK > > I have checked and verified the following for both packages, > > - Reproducible package builds > > - SVN > > - Licence > > - Signature > > - Checksums > > > > On Tue, Apr 21, 2026 at 6:37 PM Shahar Epstein <[email protected]> > wrote: > > > >> +1 (binding) for both Core & SDK, checked: > >> > >> - Reproducible build > >> - SVN > >> - Licenses > >> - Signatures > >> - Checksums > >> > >> > >> Shahar > >> > >> On Tue, Apr 21, 2026 at 7:09 AM Rahul Vats <[email protected]> > wrote: > >> > >>> Hey fellow Airflowers, > >>> > >>> The release candidates for Apache Airflow 3.2.1rc3 and Task SDK > 1.2.1rc3 > >>> are now available for testing! > >>> > >>> This email is calling for a vote on the release, which will last at > least > >>> 24 hours, from Tuesday, April 21, 2026 at 4:00 AM UTC > >>> until Wednesday, April 22, 2026 at 4:00 AM UTC > >>> < > >>> > >>> > >> > https://www.timeanddate.com/worldclock/fixedtime.html?msg=8&iso=20260422T04&p1=1440 > >>>> , > >>> and until 3 binding +1 votes have been received. > >>> > >>> Status of testing of the release is kept in > >>> https://github.com/apache/airflow/issues/65336 > >>> > >>> Airflow 3.2.1rc3 is available at: > >>> https://dist.apache.org/repos/dist/dev/airflow/3.2.1rc3/ > >>> > >>> "apache-airflow" Meta package: > >>> - *apache-airflow-3.2.1-source.tar.gz* is a source release that comes > >> with > >>> INSTALL instructions. > >>> - *apache-airflow-3.2.1.tar.gz* is the binary Python "sdist" release. > >>> - *apache_airflow-3.2.1-py3-none-any.whl* is the binary Python wheel > >>> "binary" release. > >>> > >>> "apache-airflow-core" package: > >>> - *apache_airflow_core-3.2.1.tar.gz* is the binary Python "sdist" > >> release. > >>> - *apache_airflow_core-3.2.1-py3-none-any.whl* is the binary Python > wheel > >>> "binary" release. > >>> > >>> Task SDK 1.2.1 is available at: > >>> https://dist.apache.org/repos/dist/dev/airflow/task-sdk/1.2.1rc3/ > >>> > >>> "apache-airflow-task-sdk" package: > >>> - *apache_airflow_task_sdk-1.2.1.tar.gz* is the binary Python "sdist" > >>> release. > >>> - *apache_airflow_task_sdk-1.2.1-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.1 for Airflow package and 1.2.1 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.1 > >>> > >>> Release Notes: > >>> - https://github.com/apache/airflow/blob/3.2.1rc3/RELEASE_NOTES.rst > >>> - > >>> > >>> > >> > https://airflow.staged.apache.org/docs/apache-airflow/3.2.1/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.1rc3 \ > >>> apache-airflow-core==3.2.1rc3 \ > >>> apache-airflow-task-sdk==1.2.1rc3 > >>> > >>> Constraints files are at > >>> https://github.com/apache/airflow/tree/constraints-3.2.1rc3 > >>> > >>> > >>> Regards, > >>> Rahul Vats > >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
