+1 non-binding. I ran a few example DAGs. *Ankit Chaurasia* HomePage <https://ankitchaurasia.info/> | LinkedIn <https://www.linkedin.com/in/sunank200/> | +91-9987351649
On Thu, Aug 28, 2025 at 1:27 PM Wei Lee <[email protected]> wrote: > +1 non-binding. Tested a few dags. > > Best, > Wei > > > On Aug 28, 2025, at 3:19 PM, Amogh Desai <[email protected]> wrote: > > > > +1 binding. > > > > For both airflow-core 3.0.6 RC2 and task-sdk 1.0.6 RC2: > > - Checked reproducible package builds > > - Performed SVN checks > > - Checked Licenses > > - Checked Signatures > > - Checked SHA512 checksums > > > > Ran the release candidate with breeze, and tested some dags from > > my test set (nothing specific), no concerns from me. > > > > > > Thanks & Regards, > > Amogh Desai > > > > > > On Wed, Aug 27, 2025 at 9:18 PM Hussein Awala <[email protected]> wrote: > > > >> +1 binding, checked signatures and checksums > >> > >> On Wednesday, August 27, 2025, Ash Berlin-Taylor <[email protected]> > wrote: > >> > >>> +1 binding > >>> > >>>> On 27 Aug 2025, at 10:04, Ephraim Anierobi <[email protected] > > > >>> wrote: > >>>> > >>>> +1 binding: Checked reproducibility, licences, signatures and checksum > >>> for > >>>> both sdk and core > >>>> > >>>> On Tue, 26 Aug 2025 at 22:14, Jarek Potiuk <[email protected]> wrote: > >>>> > >>>>> +1 (binding): airflow-core 3.0.6rc2: svn, reproducible build, > >> licences, > >>>>> signatures, checksums > >>>>> +1 (binding): tasl-sdk 1.0.6rc2: svn, reproducible build, licences, > >>>>> signatures, checksums > >>>>> > >>>>> I've run airflow 3.0.6rc1 + task-sdk 1.0.6rc2 in the breeze env with > >> few > >>>>> dags. Checked docs. All looks good. > >>>>> > >>>>> * We do not seem to have "issue" status" - which makes it a bit > >>> difficult > >>>>> to check if all the things I was involved in are fixed - but I looked > >> at > >>>>> https://github.com/apache/airflow/pull/54923/ for commits and except > >>> the > >>>>> "ci/dev" the doc for backfill UI is present at > >>>>> > >>>>> https://airflow.staged.apache.org/docs/apache-airflow/ > >>> stable/core-concepts/backfill.html > >>>>> > >>>>> * Also checked that the container image has the latest uv version as > >> per > >>>>> latest upgrade > >>>>> > >>>>> Jens: > >>>>> > >>>>>> Keeping me busy with release tests every second day makes me think I > >>>>>> need to further automate my release tests :-D > >>>>> > >>>>> (Maybe) controversial opinion: > >>>>> > >>>>> Actually - to be honest - I think it's the fact that we actually make > >>> some > >>>>> deliberate effort is what makes it matter. If we automate everything, > >> we > >>>>> might even not notice that something breaks, so there should be > enough > >>>>> points of pause and reflection for humans to be able to spot > >> automation > >>>>> mistakes. And we seem to do a great job on it. Every now and then we > >>> keep > >>>>> on finding new issues that we fix because we **noticed**. It would be > >>>>> impossible if all that is automated from end-2-end and humans are > >>> removed > >>>>> from all the check, > >>>>> > >>>>> In a way having 3-4 releases when we find no problems with the > >> process, > >>>>> means that we probably missed something or automated it too much. > >>>>> > >>>>> J. > >>>>> > >>>>> On Tue, Aug 26, 2025 at 10:31 PM Jens Scheffler > >>> <[email protected] > >>>>>> > >>>>> wrote: > >>>>> > >>>>>> Hi Kaxil, > >>>>>> > >>>>>> Keeping me busy with release tests every second day makes me think I > >>>>>> need to further automate my release tests :-D > >>>>>> > >>>>>> Checked Airflow-Core 3.0.6RC2: +1 (binding) - Checked SVN, > >> Reproducible > >>>>>> package build, Licenses, Signatures > >>>>>> > >>>>>> Checked Task-SDK 1.0.6RC2: +1 (binding) - Checked SVN, Reproducible > >>>>>> package build, Licenses, Signatures > >>>>>> > >>>>>> Like last time: Used breeze and the *.0.6rc2 with current > >> EdgeExecutor > >>>>>> and started the "integration test" Dag - all with success, looking > >>> good! > >>>>>> > >>>>>> Thanks for the efforts! > >>>>>> > >>>>>> Jens > >>>>>> > >>>>>> On 26.08.25 16:44, Kaxil Naik wrote: > >>>>>>> Hey fellow Airflowers, > >>>>>>> > >>>>>>> The release candidates for *Apache Airflow 3.0.6rc2 *and *Task SDK > >>>>>>> 1.0.6rc2* are > >>>>>>> now available for testing! > >>>>>>> > >>>>>>> This email is calling for a vote on the release, which will last at > >>>>> least > >>>>>>> until *29th Aug* and until 3 binding +1 votes have been received. > >>>>>>> > >>>>>>> Consider this my +1 binding vote. > >>>>>>> > >>>>>>> Airflow 3.0.6rc2 is available at: > >>>>>>> https://dist.apache.org/repos/dist/dev/airflow/3.0.6rc2/ > >>>>>>> > >>>>>>> "apache-airflow" Meta package: > >>>>>>> > >>>>>>> - *apache-airflow-3.0.6-source.tar.gz* is a source release that > >>>>> comes > >>>>>>> with INSTALL instructions. > >>>>>>> - *apache-airflow-3.0.6.tar.gz* is the binary Python "sdist" > >>>>> release. > >>>>>>> - *apache_airflow-3.0.6-py3-none-any.whl* is the binary Python > >>>>> wheel > >>>>>>> "binary" release. > >>>>>>> > >>>>>>> > >>>>>>> "apache-airflow-core" package > >>>>>>> > >>>>>>> - *apache_airflow_core-3.0.6.tar.gz* is the binary Python "sdist" > >>>>>>> release. > >>>>>>> - *apache_airflow_3.0.6-py3-none-any.whl* is the binary Python > >>>>> wheel > >>>>>>> "binary" release. > >>>>>>> > >>>>>>> > >>>>>>> Task SDK 1.0.6rc2 is available at: > >>>>>>> https://dist.apache.org/repos/dist/dev/airflow/task-sdk/1.0.6rc2/ > >>>>>>> > >>>>>>> "apache-airflow-task-sdk" package > >>>>>>> > >>>>>>> - *apache_airflow_task_sdk-1.0.6.tar.gz* is the binary Python > >>>>> "sdist" > >>>>>>> release. > >>>>>>> - *apache_airflow_task_sdk-1.0.6-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.0.6 for Airflow package and 1.0.6 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.0.6 > >>>>>>> *Release Notes*: > >>>>>>> > >>>>>>> - > https://github.com/apache/airflow/blob/3.0.6rc2/RELEASE_NOTES.rst > >>>>>>> - > >>>>>>> > >>>>>> > >>>>> https://airflow.staged.apache.org/docs/apache-airflow/3.0.6/ > >>> 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.0.6rc2 --pre > >>>>>>> ``` > >>>>>>> > >>>>>>> Constraints files are at > >>>>>>> https://github.com/apache/airflow/tree/constraints-3.0.6rc2 > >>>>>>> > >>>>>>> Regards, > >>>>>>> Kaxil > >>>>>>> > >>>>>> > >>>>>> > --------------------------------------------------------------------- > >>>>>> To unsubscribe, e-mail: [email protected] > >>>>>> For additional commands, e-mail: [email protected] > >>>>>> > >>>>>> > >>>>> > >>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [email protected] > >>> For additional commands, e-mail: [email protected] > >>> > >>> > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
