Yeah. I think Amogh was more saying that it's not binding - which you also stated.
While you can do it (nothing to block it) it's not necessarily expected that you do it, because it does not add value to the legal check (which has to be done anyway by 3 PMC members and that constitutes the legal act of the Foundation to release the software). There is nothing wrong with doing it of course - especially if you find any issues with reproducibility or other checks - please absolutely report it - the +1 check by PMC in this form are only valid e aww but I think more important in this case is to actually check if airflow works. The message was really to clarify what's the purpose of it - and it's great to remind the reason why we are doing it - because just doing and repeating such checks without knowing the purpose of it might - in a long term - turn into a 'cargo cult' If we do not understand why we are doing it - when we just repeat something without deeper understanding why. J On Wed, Feb 4, 2026, 07:29 Shivam Rastogi <[email protected]> wrote: > Hi Amogh, > > Thanks for the clarification. > > Just to clarify - I did actually perform all the checks I listed. I cloned > the SVN repo, built reproducible packages using breeze release-management > commands, ran Apache RAT, verified GPG signatures (via Docker since my host > GPG was too old), and checked SHA512 checksums. The artifacts matched. > > Question: What do you mean by these checks cannot be performed even if > non-PMC members wish to? > > Regards, > Shivam > > On Tue, 3 Feb 2026 at 22:17, Amogh Desai <[email protected]> wrote: > > > Shivam -- Thanks a lot for taking the time to test and verify the RC, we > > appreciate > > the effort. > > > > Just a quick clarification for release related checks in Apache Airflow: > > Legal checks such as SVN, reproducible package builds, checksums, and > > licenses can only be performed by PMC members as per > > > > > https://github.com/apache/airflow/blob/main/dev/README_RELEASE_AIRFLOW.md#verify-the-release-candidate-by-pmc-members > > . > > Non PMC members will not be able to perform such > > checks even if they wish to. > > > > That said, the functional testing you did is very helpful and we > encourage > > that. > > > > For future -- refrain from voting on checks you didn't perform. > > Thanks & Regards, > > Amogh Desai > > > > > > On Wed, Feb 4, 2026 at 11:28 AM Shivam Rastogi <[email protected]> > > wrote: > > > > > +1 (non-binding) > > > > > > I verified the following on Amazon Linux 2: > > > > > > Airflow/Airflow Core 3.1.7rc2: > > > - SVN > > > - Reproducible package build > > > - Licenses (Apache RAT) > > > - Signatures (verified via Docker/Ubuntu 22.04) > > > - Checksums (SHA512) > > > > > > Task SDK 1.1.7rc2: > > > - SVN > > > - Reproducible package build > > > - Signatures > > > - Checksums > > > > > > Functional Testing: > > > - Started Airflow via Breeze with --use-airflow-version 3.1.7rc2 > > > - Tested AthenaOperator using a simple DAG against real AWS account > > > - Query executed successfully > > > > > > No blocking issues found. > > > > > > This is my first verification - happy to contribute! > > > > > > Thanks and regards, > > > Shivam Rastogi > > > > > > On Tue, 3 Feb 2026 at 21:42, Amogh Desai <[email protected]> > wrote: > > > > > > > +1 binding. > > > > > > > > For both airflow-core 3.1.7rc2 and task sdk 1.1.7rc2: > > > > > > > > - Checked SVN > > > > - Checked in Docker > > > > - Checked reproducible package builds > > > > - Checked licenses > > > > - Checked signatures > > > > > > > > Installed the RC and ran some of my test dags. > > > > The issue with pyjwt seems to be fixed, 2.11.0 gets installed by > > default > > > as > > > > well > > > > as the login seems to work fine for Airflow UI. > > > > > > > > Thanks & Regards, > > > > Amogh Desai > > > > > > > > > > > > On Wed, Feb 4, 2026 at 2:19 AM Buğra Öztürk <[email protected] > > > > > > wrote: > > > > > > > > > +1 (binding) for both Airflow/Airflow Core and TaskSDK releases. I > > have > > > > > checked, > > > > > Airflow/Airflow Core: > > > > > - SVN > > > > > - Reproducible package builds > > > > > - Licence > > > > > - Signature > > > > > - Checksums > > > > > TaskSDK: > > > > > - SVN > > > > > - Reproducible package builds > > > > > - Licence > > > > > - Signature > > > > > - Checksums > > > > > > > > > > On Tue, Feb 3, 2026 at 3:43 PM Jarek Potiuk <[email protected]> > > wrote: > > > > > > > > > > > +1 (binding): > > > > > > > > > > > > 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 > > > > > > > > > > > > I also checked that the PyJWT issue is solved - the > lower-bounding > > > > works > > > > > > for "regular" installation without constraints. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Feb 3, 2026 at 12:21 PM Ephraim Anierobi < > > > > > > [email protected]> > > > > > > wrote: > > > > > > > > > > > > > Hey fellow Airflowers, > > > > > > > > > > > > > > The release candidates for Apache Airflow 3.1.7rc2 and Task SDK > > > > > 1.1.7rc2 > > > > > > > are now available for testing! > > > > > > > > > > > > > > This email is calling for a vote on the release, which will > last > > at > > > > > least > > > > > > > 24 hours, from Tuesday, February 3, 2026 at 11:15 am UTC > > > > > > > until Wednesday, February 4, 2026 at 11:15 pm UTC > > > > > > > < > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://www.timeanddate.com/worldclock/fixedtime.html?msg=8&iso=20260204T1115&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/61255 > > > > > > > > > > > > > > Consider this my +1 binding vote. > > > > > > > > > > > > > > Airflow 3.1.7rc2 is available at: > > > > > > > https://dist.apache.org/repos/dist/dev/airflow/3.1.7rc2/ > > > > > > > > > > > > > > "apache-airflow" Meta package: > > > > > > > - *apache-airflow-3.1.7-source.tar.gz* is a source release that > > > comes > > > > > > with > > > > > > > INSTALL instructions. > > > > > > > - *apache-airflow-3.1.7.tar.gz* is the binary Python "sdist" > > > release. > > > > > > > - *apache_airflow-3.1.7-py3-none-any.whl* is the binary Python > > > wheel > > > > > > > "binary" release. > > > > > > > > > > > > > > "apache-airflow-core" package: > > > > > > > - *apache_airflow_core-3.1.7.tar.gz* is the binary Python > "sdist" > > > > > > release. > > > > > > > - *apache_airflow_core-3.1.7-py3-none-any.whl* is the binary > > Python > > > > > wheel > > > > > > > "binary" release. > > > > > > > > > > > > > > Task SDK 1.1.7 is available at: > > > > > > > > > https://dist.apache.org/repos/dist/dev/airflow/task-sdk/1.1.7rc2/ > > > > > > > > > > > > > > "apache-airflow-task-sdk" package: > > > > > > > - *apache_airflow_task_sdk-1.1.7.tar.gz* is the binary Python > > > "sdist" > > > > > > > release. > > > > > > > - *apache_airflow_task_sdk-1.1.7-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.1.7 for Airflow package and 1.1.7 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.1.7 > > > > > > > > > > > > > > Release Notes: > > > > > > > - > > > https://github.com/apache/airflow/blob/3.1.7rc2/RELEASE_NOTES.rst > > > > > > > - > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://airflow.staged.apache.org/docs/apache-airflow/3.1.7/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.1.7rc2 \ > > > > > > > apache-airflow-core==3.1.7rc2 \ > > > > > > > apache-airflow-task-sdk==1.1.7rc2 > > > > > > > > > > > > > > Constraints files are at > > > > > > > https://github.com/apache/airflow/tree/constraints-3.1.7rc2 > > > > > > > > > > > > > > Changes since rc1 > > > > > > > - Fix JWT token generation with unset issuer/audience config > > > (#61331) > > > > > > > > > > > > > > Cheers, > > > > > > > Ephraim > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Bugra Ozturk > > > > > > > > > > > > > > >
