+ 1 (non-binding)

verify the newly generated pool model.

Yes, as mentioned by Pierre Jeambrun there is
apache-airflow-client-2.6.0-source archive inside 2.6.1 source. It would be
great if we can clean it.

On Mon, May 22, 2023 at 4:17 AM Pierre Jeambrun <pierrejb...@gmail.com>
wrote:

> +1 (binding), same.
>
> I don't think this is blocking but we have the
> `apache-airflow-client-2.6.0-source` archive inside the 2.6.1 source
> archive, must be some leftovers from the last release.
>
> Le dim. 21 mai 2023 à 11:24, Jarek Potiuk <ja...@potiuk.com> a écrit :
>
> > +1 (binding). Tested the client. checked licences, signatures, checksums
> -
> > all looks good!.
> >
> > Sorry for the delay, I was sure I did it already :).
> >
> > On Wed, May 17, 2023 at 3:14 PM Ephraim Anierobi <
> > ephraimanier...@apache.org>
> > wrote:
> >
> > > Hey fellow Airflowers,
> > >
> > > I have cut the first release candidate for the Airflow Python Client
> > > 2.6.1rc1.
> > > The client consists of APIs corresponding to REST APIs available in
> > > *Apache Airflow 2.6.1*. This email is calling for a vote on
> > > the release, which will last for 72 hours.
> > >
> > > Consider this my (binding) +1.
> > >
> > > Airflow Client 2.6.1rc1 is available at:
> > >
> https://dist.apache.org/repos/dist/dev/airflow/clients/python/2.6.1rc1/
> > >
> > > Or also available at PyPI:
> > > https://pypi.org/project/apache-airflow-client/2.6.1rc1/
> > >
> > > *apache-airflow-client-2.6.1rc1-source.tar.gz* is a source release that
> > > comes with
> > > INSTALL instructions.
> > > *apache-airflow-client-2.6.1rc1-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 fixes:*
> > > - Fix Pool schema OpenAPI spec (#30973)
> > >
> > > Cheers,
> > > Ephraim
> > >
> >
>

Reply via email to