+1 non-binding (concurring with Phani)

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 Tue, Nov 29, 2022 at 12:26 PM Phani Kumar
<phani.ku...@astronomer.io.invalid> wrote:

> +1 non-binding. All our DAGs ran successfully with the below providers.
>
> apache-airflow-providers-amazon==6.2.0rc3,
> apache-airflow-providers-common-sql==1.3.1rc3,
> apache-airflow-providers-databricks==4.0.0rc3,
> apache-airflow-providers-google==8.6.0rc3,
> apache-airflow-providers-snowflake==4.0.1rc3
>
> On Tue, Nov 29, 2022 at 1:37 AM Jarek Potiuk <ja...@potiuk.com> wrote:
>
>> I'd love some votes. Testing looks cool  (seems that the problems are
>> fixed) I would love to release the providers tomorrow mid-day, right
>> after the voting period passes as (as expected) some of our users are
>> suffering from the compatibility issues of the common.sql provider and
>> waiting for the fix.
>>
>> On Sat, Nov 26, 2022 at 12:06 PM Jarek Potiuk <ja...@potiuk.com> wrote:
>> >
>> > Hey all,
>> >
>> > I have just cut the new wave Airflow Providers packages. This email is
>> > calling a vote on the release, which will last for 72 hours -
>> > which means that it will end on Tue 29 Nov 12:00:00 CET 2022.
>> > Most of the changes has already been tested and we are past Thanksgiving
>> > so it should be pretty straightforward - we also want to release the
>> providers
>> > ideally before 2.5 is out to make sure 2.5 will have the right
>> > constraints on them.
>> >
>> > Consider this my (binding) +1.
>> >
>> > ### DESCRIPTION OF THE RELEASE
>> >
>> > This is a follow-up release after the November release. Mostly it's
>> > about fixing problems we found after release with common.sql provider
>> > and its interaction with google/databricks/other providers - fixing the
>> > problems found in the rc2 wave of providers. Also this
>> > release contains asana, jdbc, and yandex which were removed from the
>> > previous wave.
>> >
>> > After this release is complete, all the providers will have min airflow
>> version
>> > set to 2.3 - which means that they have the requirements set to
>> >
>> > apache-airflow>=2.3.0
>> >
>> > Those providers that depend on common-sql will have
>> > common-sql >= 1.3.1
>> >
>> > This will also help in the future to remove
>> > some of the common code which we had to add back in 1.3.1.
>> >
>> > Once common-sql 1.3.1 is released, we will yank common-sql 1.3.0
>> > because it breaks google provider 8.4.0.
>> >
>> > ### END OF DESCRIPTION OF THE RELEASE
>> >
>> > 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 who would like to test the RC
>> > candidates are described in
>> >
>> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#verify-the-release-by-pmc-members
>> >
>> > and for Contributors:
>> >
>> >
>> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#verify-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/27939
>> >
>> > You can find packages as well as detailed changelog following the below
>> links:
>> >
>> > https://pypi.org/project/apache-airflow-providers-amazon/6.2.0rc3/
>> >
>> https://pypi.org/project/apache-airflow-providers-apache-drill/2.3.1rc3/
>> >
>> https://pypi.org/project/apache-airflow-providers-apache-druid/3.3.1rc3/
>> > https://pypi.org/project/apache-airflow-providers-apache-hive/4.1.1rc3/
>> >
>> https://pypi.org/project/apache-airflow-providers-apache-pinot/4.0.1rc3/
>> > https://pypi.org/project/apache-airflow-providers-asana/2.1.0rc3/
>> > https://pypi.org/project/apache-airflow-providers-common-sql/1.3.1rc3/
>> > https://pypi.org/project/apache-airflow-providers-databricks/4.0.0rc3/
>> >
>> https://pypi.org/project/apache-airflow-providers-elasticsearch/4.3.1rc3/
>> > https://pypi.org/project/apache-airflow-providers-exasol/4.1.1rc3/
>> > https://pypi.org/project/apache-airflow-providers-google/8.6.0rc3/
>> > https://pypi.org/project/apache-airflow-providers-jdbc/3.3.0rc3/
>> >
>> https://pypi.org/project/apache-airflow-providers-microsoft-mssql/3.3.1rc3/
>> > https://pypi.org/project/apache-airflow-providers-mysql/3.4.0rc3/
>> > https://pypi.org/project/apache-airflow-providers-neo4j/3.2.1rc3/
>> > https://pypi.org/project/apache-airflow-providers-odbc/3.2.1rc3/
>> > https://pypi.org/project/apache-airflow-providers-oracle/3.5.1rc3/
>> > https://pypi.org/project/apache-airflow-providers-postgres/5.3.1rc3/
>> > https://pypi.org/project/apache-airflow-providers-presto/4.2.0rc3/
>> > https://pypi.org/project/apache-airflow-providers-qubole/3.3.1rc3/
>> > https://pypi.org/project/apache-airflow-providers-slack/7.1.0rc3/
>> > https://pypi.org/project/apache-airflow-providers-snowflake/4.0.1rc3/
>> > https://pypi.org/project/apache-airflow-providers-sqlite/3.3.1rc3/
>> > https://pypi.org/project/apache-airflow-providers-trino/4.3.0rc3/
>> > https://pypi.org/project/apache-airflow-providers-vertica/3.3.1rc3/
>> > https://pypi.org/project/apache-airflow-providers-yandex/3.2.0rc3/
>> >
>> > Cheers,
>> >
>> > J.
>>
>

Reply via email to