+1 non-binding I tested our example DAGs for asynchronous providers kept in astronomer-providers, verified that the version works well and does not have a regression on our suite.
Regards, Pankaj Koti *Senior Software Engineer, *OSS Engineering Team. Location: Pune, India Timezone: Indian Standard Time (IST) Email: pankaj.k...@astronomer.io Mobile: +91 9730079985 On Thu, May 11, 2023 at 3:07 PM Ephraim Anierobi <ephraimanier...@apache.org> wrote: > Hey fellow Airflowers, > > I have cut Airflow 2.6.1rc1. This email is calling a vote on the release, > which will last at least 72 hours, from Thursday, May 11, 2023 at 09:35 am > UTC > until Sunday, May 14, 2023 at 09:35 am UTC > < > https://www.timeanddate.com/worldclock/fixedtime.html?msg=8&iso=20230514T0935&p1=1440 > >, > and until 3 binding +1 votes have been received. > > Status of testing of the release is kept at > https://github.com/apache/airflow/issues/31202 > > Consider this my (binding) +1. > > Airflow 2.6.1rc1 is available at: > https://dist.apache.org/repos/dist/dev/airflow/2.6.1rc1/ > > *apache-airflow-2.6.1-source.tar.gz* is a source release that comes with > INSTALL instructions. > *apache-airflow-2.6.1.tar.gz* is the binary Python "sdist" release. > *apache_airflow-2.6.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 PMCs and Contributors who would like to test this RC > are described in > > https://github.com/apache/airflow/blob/main/dev/README_RELEASE_AIRFLOW.md\#verify-the-release-candidate-by-pmcs > > Please note that the version number excludes the `rcX` string, so it's now > simply 2.6.1. This will allow us to rename the artifact without modifying > the artifact checksums when we actually release. > > Release Notes: > https://github.com/apache/airflow/blob/2.6.1rc1/RELEASE_NOTES.rst > > Changes since 2.6.0: > *Bug Fixes* > - Fix timestamp parse failure for k8s executor pod tailing (#31175) > - Make sure that DAG processor job row has filled value in ``job_type`` > column (#31182) > - Fix section name reference for ``api_client_retry_configuration`` > (#31174) > - Ensure the KPO runs pod mutation hooks correctly (#31173) > - Remove worrying log message about redaction from the OpenLineage plugin > (#31149) > - Move ``interleave_timestamp_parser`` config to the logging section > (#31102) > - Ensure that we check worker for served logs if no local or remote logs > found (#31101) > - Fix ``MappedTaskGroup`` import in taskinstance file (#31100) > - Format DagBag.dagbag_report() Output (#31095) > - Mask task attribute on task detail view (#31125) > - Fix template error when iterating None value and fix params documentation > (#31078) > - Fix ``apache-hive`` extra so it installs the correct package (#31068) > - Fix issue with zip files in DAGs folder when pre-importing Airflow > modules (#31061) > - Move TaskInstanceKey to a separate file to fix circular import (#31033) > - Fix deleting DagRuns and TaskInstances that have a note (#30987) > - Fix ``airflow providers get`` command output (#30978) > - Fix Pool schema in the OpenAPI spec (#30973) > - Add support for dynamic tasks with template fields that contain > ``pandas.DataFrame`` (#30943) > - Use the Task Group explicitly passed to 'partial' if any (#30933) > - Fix ``order_by`` request in list DAG rest api (#30926) > - Include node height/width in center-on-task logic (#30924) > - Remove print from dag trigger command (#30921) > - Improve task group UI in new graph (#30918) > - Fix mapped states in grid view (#30916) > - Fix problem with displaying graph (#30765) > - Fix backfill KeyError when try_number out of sync (#30653) > - Re-enable clear and setting state in the TaskInstance UI (#30415) > - Prevent DagRun's ``state`` and ``start_date`` from being reset when > clearing a task in a running DagRun (#30125) > > *Misc/Internal* > - Show task instances affected by clearing in a table (#30633) > - Fix missing models in API documentation (#31021) > > *Doc only changes* > - Improve description of the ``dag_processing.processes`` metric (#30891) > - Improve Quick Start instructions (#30820) > - Add section about missing task logs to the FAQ (#30717) > - Mount the ``config`` directory in docker compose (#30662) > - Update ``version_added`` config field for ``might_contain_dag`` and > ``metrics_allow_list`` (#30969) > > Cheers, > Ephraim >
