+1 (binding)

On Sunday, February 18, 2024, Elad Kalif <elad...@apache.org> wrote:

> provider cncf.kubernetes will be excluded from this release
>
> On Sun, Feb 18, 2024 at 11:32 AM Pankaj Koti
> <pankaj.k...@astronomer.io.invalid> wrote:
>
> > -1 (non-binding) for apache-airflow-providers-cncf-kubernetes/8.0.0rc2/
> > <
> > https://pypi.org/project/apache-airflow-providers-cncf-
> kubernetes/8.0.0rc2/
> > >
> > The happy cases are working fine for cncf k8s, however, I am observing
> > an issue with the recent modifications to KPO included in the RC, where
> > after the desired timeout has reached waiting for the pod to start, the
> KPO
> > task should fail but instead its hanging.
> > I have identified the cause for this and created a fix PR
> > https://github.com/apache/airflow/pull/37514.
> > Requesting reviews on the fix PR.
> >
> >
> > +1 (non-binding) for Amazon and common-sql
> >
> > Best regards,
> >
> > *Pankaj Koti*
> > Senior Software Engineer (Airflow OSS Engineering team)
> > Location: Pune, Maharashtra, India
> > Timezone: Indian Standard Time (IST)
> > Phone: +91 9730079985
> >
> >
> > On Sun, Feb 18, 2024 at 3:00 PM Andrey Anshin <andrey.ans...@taragol.is>
> > wrote:
> >
> > > +1 (binding)
> > >
> > > Verify signatures, checksums, files
> > >
> > >
> > > On Sun, 18 Feb 2024 at 11:09, Jarek Potiuk <ja...@potiuk.com> wrote:
> > >
> > > > +1 (binding). Checked my changes, Verified reproducibility,
> signatures,
> > > > licences, checksums, all looks good.
> > > >
> > > > On Sun, Feb 18, 2024 at 6:10 AM Amogh Desai <
> amoghdesai....@gmail.com>
> > > > wrote:
> > > >
> > > > > +1 non binding
> > > > >
> > > > > On Sun, 18 Feb 2024 at 9:37 AM, Wei Lee <weilee...@gmail.com>
> wrote:
> > > > >
> > > > > > +1 (non-binding)
> > > > > >
> > > > > > Tested both providers with our example DAGs without encountering
> an
> > > > > error.
> > > > > > Verified #36330 <https://github.com/apache/airflow/pull/36330>
> > > > > > Best,
> > > > > >
> > > > > > Wei
> > > > > >
> > > > > >
> > > > > > > On Feb 17, 2024, at 5:51 PM, ayaan rayan <
> > > ayaanrayaan9...@gmail.com>
> > > > > > wrote:
> > > > > > >
> > > > > > > ‫بتاریخ ہفتہ، 17 فروری، 2024 بوقت 1:22 PM‏ ‪Elad Kalif‬‏
> > > > > > > <‪elad...@apache.org‬‏> نے لکھا:‬
> > > > > > >>
> > > > > > >> Hey all,
> > > > > > >>
> > > > > > >> I have just cut the RC2/RC3 wave Airflow Providers packages.
> > This
> > > > > email
> > > > > > is
> > > > > > >> calling a vote on the release,
> > > > > > >> which will last for *24 hours* - which means that it will end
> on
> > > > > > February
> > > > > > >> 18, 2024 08:20 AM UTC and until 3 binding +1 votes have been
> > > > received.
> > > > > > Vote
> > > > > > >> duration is according to a shortened voting period policy as
> > > > accepted
> > > > > in
> > > > > > >> this thread
> > > > > > >> <
> > https://lists.apache.org/thread/cv194w1fqqykrhswhmm54zy9gnnv6kgm
> > > >.
> > > > > > >>
> > > > > > >>
> > > > > > >> Consider this my (binding) +1.
> > > > > > >>
> > > > > > >> Airflow Providers are available at:
> > > > > > >> https://dist.apache.org/repos/dist/dev/airflow/providers/
> > > > > > >>
> > > > > > >> *apache-airflow-providers-<PROVIDER>-*.tar.gz* are the binary
> > > > > > >> Python "sdist" release - they are also official "sources" for
> > the
> > > > > > provider
> > > > > > >> packages.
> > > > > > >>
> > > > > > >> *apache_airflow_providers_<PROVIDER>-*.whl are the binary
> > > > > > >> Python "wheel" release.
> > > > > > >>
> > > > > > >> The test procedure for PMC members is described in
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> > https://github.com/apache/airflow/blob/main/dev/README_
> RELEASE_PROVIDER_PACKAGES.md#verify-the-release-candidate-by-pmc-members
> > > > > > >>
> > > > > > >> The test procedure for and Contributors who would like to test
> > > this
> > > > RC
> > > > > > is
> > > > > > >> described in:
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> > https://github.com/apache/airflow/blob/main/dev/README_
> RELEASE_PROVIDER_PACKAGES.md#verify-the-release-candidate-by-contributors
> > > > > > >>
> > > > > > >>
> > > > > > >> 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 members of the
> > > > community
> > > > > > are
> > > > > > >> encouraged to test the release and vote with "(non-binding)".
> > > > > > >>
> > > > > > >> Please note that the version number excludes the 'rcX' string.
> > > > > > >> This will allow us to rename the artifact without modifying
> > > > > > >> the artifact checksums when we actually release.
> > > > > > >>
> > > > > > >> The status of testing the providers by the community is kept
> > here:
> > > > > > >> https://github.com/apache/airflow/issues/37504
> > > > > > >>
> > > > > > >> The issue is also the easiest way to see important PRs
> included
> > in
> > > > the
> > > > > > RC
> > > > > > >> candidates.
> > > > > > >> Detailed changelog for the providers will be published in the
> > > > > > documentation
> > > > > > >> after the
> > > > > > >> RC candidates are released.
> > > > > > >>
> > > > > > >> You can find the RC packages in PyPI following these links:
> > > > > > >>
> > > > > > >>
> > > https://pypi.org/project/apache-airflow-providers-amazon/8.18.0rc2/
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> > https://pypi.org/project/apache-airflow-providers-cncf-
> kubernetes/8.0.0rc2/
> > > > > > >>
> > > > >
> > > https://pypi.org/project/apache-airflow-providers-
> common-sql/1.11.0rc3/
> > > > > > >>
> > > > > > >> Cheers,
> > > > > > >> Elad Kalif
> > > > > > >
> > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> > > > > > > For additional commands, e-mail: dev-h...@airflow.apache.org
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Reply via email to