(Elad asked me to take over from here as he is flying tonight) I am cancelling this vote due to the problem found by Andrey - https://github.com/apache/airflow/issues/36948#issuecomment-1909664795 - the problem is that the way logger_name passing and **kwargs handling, there was a potential of using the hooks in a way that would be breaking compatibility with past versions of Airflow. We've already reverted https://github.com/apache/airflow/pull/36675 which triggered it and I will prepare the RC2 for all the providers here that actually had changes from the previous release (this is the fastest way) with accelerated vote.
Then we will proceed with a better and more backwards-compatible way of implementing what #36675 aimed to achieve and release the next wave J. On Thu, Jan 25, 2024 at 8:52 AM Pankaj Singh <ags.pankaj1...@gmail.com> wrote: > +1 (non-binding). > > ran some tests for amazon,google,ftp,snowflake,databricks,openlineage,mysql > providers. > > On Thu, Jan 25, 2024 at 4:17 AM Jed Cunningham <jedcunning...@apache.org> > wrote: > > > +1 (binding) checked binary reproduction, licences, signatures, and > > checksums. > > > > On my system the binary reproduction check for the source tarball did > fail, > > but I spot verified the tarball contents are correct. I'm still > > investigating, but no reason to hold the release for this. > > >
