+1 (binding). Tested, licences, sources, checksums. Verified source code by
regenerating the client and comparing the output. Tested
`test_python_client.py` with it. All looks fine.

On Tue, Dec 19, 2023 at 3:36 PM Wei Lee <[email protected]> wrote:

> +1 (non-binding)
>
> Best,
> Wei
>
> > On Dec 19, 2023, at 8:20 PM, utkarsh sharma <[email protected]>
> wrote:
> >
> > +1 non binding
> >
> > On Tue, 19 Dec 2023 at 5:23 PM, Amogh Desai <[email protected]>
> > wrote:
> >
> >> +1 non binding
> >>
> >> Installed the RC bits and ran example DAGs.
> >>
> >>
> >>
> >> On Tue, 19 Dec 2023 at 5:22 PM, Phani Kumar
> >> <[email protected]> wrote:
> >>
> >>> +1 non binding
> >>>
> >>> On Tue, Dec 19, 2023 at 5:10 PM Pankaj Koti
> >>> <[email protected]> wrote:
> >>>
> >>>> +1 (non-binding)
> >>>>
> >>>> Installed the RC and was able to trigger a DAG successfully using the
> >>>> client.
> >>>>
> >>>> Best regards,
> >>>>
> >>>> *Pankaj Koti*
> >>>> Senior Software Engineer (Airflow OSS Engineering team)
> >>>> Location: Pune, Maharashtra, India
> >>>> Timezone: Indian Standard Time (IST)
> >>>> Phone: +91 9730079985
> >>>>
> >>>>
> >>>> On Tue, Dec 19, 2023 at 3:49 PM Ephraim Anierobi <
> >>>> [email protected]>
> >>>> wrote:
> >>>>
> >>>>> Hey fellow Airflowers,
> >>>>>
> >>>>> I have cut the release candidate for the Airflow Python Client
> >>> 2.8.0rc1.
> >>>>> The client consists of APIs corresponding to REST APIs available in
> >>>>> *Apache Airflow 2.8.0*. This email is calling for a vote on
> >>>>> the release, which will last for 72 hours. Consider this my (binding)
> >>> +1.
> >>>>>
> >>>>> Airflow Client 2.8.0rc1 is available at:
> >>>>>
> >>>
> https://dist.apache.org/repos/dist/dev/airflow/clients/python/2.8.0rc1/
> >>>>>
> >>>>> Or also available at PyPI:
> >>>>> https://pypi.org/project/apache-airflow-client/2.8.0rc1/
> >>>>>
> >>>>> *apache-airflow-client-2.8.0rc1-source.tar.gz* is a source release
> >> that
> >>>>> comes with
> >>>>> INSTALL instructions.
> >>>>> *apache-airflow-client-2.8.0rc1-bin.tar.gz* is the binary Python
> >>> "sdist"
> >>>>> release.
> >>>>>
> >>>>> Public keys are available at:
> >>>>> https://dist.apache.org/repos/dist/release/airflow/KEYS
> >>>>>
> >>>>> Only votes from PMC members are binding, but the release manager
> >> should
> >>>>> encourage members of the community to test the release and vote with
> >>>>> "(non-binding)".
> >>>>>
> >>>>> *Changelog:*
> >>>>>
> >>>>> ### Major changes:
> >>>>>  - Allow filtering event logs by attributes ([#34417](
> >>>>> https://github.com/apache/airflow/pull/34417))
> >>>>>  - Add extra fields to plugins endpoint ([#34913](
> >>>>> https://github.com/apache/airflow/pull/34913))
> >>>>>  - Let auth managers provide their own API endpoints ([#34349](
> >>>>> https://github.com/apache/airflow/pull/34349))
> >>>>>  - Enable pools to consider deferred tasks ([#32709](
> >>>>> https://github.com/apache/airflow/pull/32709))
> >>>>>  - Add dag_run_ids and task_ids filter for the batch task instance
> >> API
> >>>>> endpoint ([#32705](https://github.com/apache/airflow/pull/32705))
> >>>>>
> >>>>> ### Major Fixes
> >>>>>  - Add DagModel attributes before dumping DagDetailSchema for
> >>>>> get_dag_details API endpoint ([#34947](
> >>>>> https://github.com/apache/airflow/pull/34947))
> >>>>>  - Add TriggerRule missing value in rest API ([#35194](
> >>>>> https://github.com/apache/airflow/pull/35194))
> >>>>>  - Fix wrong plugin schema ([#34858](
> >>>>> https://github.com/apache/airflow/pull/34858))
> >>>>>  - Make dry run optional for patch task instance ([#34568](
> >>>>> https://github.com/apache/airflow/pull/34568))
> >>>>>  - OpenAPI Spec fix nullable alongside $ref ([#32887](
> >>>>> https://github.com/apache/airflow/pull/32887))
> >>>>>  - Clarify new_state in OpenAPI spec ([#34056](
> >>>>> https://github.com/apache/airflow/pull/34056))
> >>>>>
> >>>>> ### NEW API supported
> >>>>>  - NA
> >>>>>
> >>>>> Cheers,
> >>>>> Ephraim
> >>>>>
> >>>>
> >>>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to