I think we can release it right after as .1 if this is so important. The voting will finish tomorrow and we can easily make an ad-hoc release of cncf.k8s only right after we release 3.0.0. Seems that it's just really bumping the K8S client library, so it should be a rather straightforward update.
J. On Tue, Jan 4, 2022 at 1:09 PM Ash Berlin-Taylor <[email protected]> wrote: > > Is it too late to include https://github.com/apache/airflow/pull/18797 (just > merged) in to cncf.kubernetes 3.0.0? > > Thanks, > Ash > > On Fri, Dec 31 2021 at 22:45:31 +0100, Jarek Potiuk <[email protected]> wrote: > > Ech.. New Year's Eve in action... Will sent it again with good subject :) On > Fri, Dec 31, 2021 at 10:44 PM Jarek Potiuk <[email protected]> wrote: > > Hey all, First of all - All the best in 2022! I wish all of you the 2022 > (after 2020 and 2021) will be relatively uneventful :). 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 + 2 days(!) for New Years Eve - which > means that it will end on Wed 05 Jan 2022 10:27:01 PM CET. Consider this my > (binding) +1. This is a regular set of provider's (20+) - but cncf.kubernetes > stands out as it has a number of improvements including a dry-run mode ! > While it is likely backwards compatible, we made a major release for it - in > case you extended KubernetesPodOperator you might need some changes. But, > afraid not! We got you covered and Daniel wrote a very detailed changelog > that covers all the changes, so it should be a _breeze_ to update to the new > version :). See more here: > https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/3.0.0rc1/ > KUDOS to Daniel for this! Also - the new providers are mostly MyPY compatible > and have improved typing - so if you are using the providers in your DAGs, > you will get a nice IDE support for autocomplete and you can run type > verification when you use it - with MyPY. We will continue improving that, > but it's already a big move forward - especially when we release Airflow > 2.3.0 (soon). 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/20615 You can find packages as well > as detailed changelog following the below links: > https://pypi.org/project/apache-airflow-providers-amazon/2.6.0rc1/ > https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/3.0.0rc1/ > https://pypi.org/project/apache-airflow-providers-yandex/2.2.0rc1/ > https://pypi.org/project/apache-airflow-providers-papermill/2.2.0rc1/ > https://pypi.org/project/apache-airflow-providers-oracle/2.1.0rc1/ > https://pypi.org/project/apache-airflow-providers-apache-druid/2.2.0rc1/ > https://pypi.org/project/apache-airflow-providers-tableau/2.1.3rc1/ > https://pypi.org/project/apache-airflow-providers-apache-spark/2.0.3rc1/ > https://pypi.org/project/apache-airflow-providers-databricks/2.2.0rc1/ > https://pypi.org/project/apache-airflow-providers-snowflake/2.4.0rc1/ > https://pypi.org/project/apache-airflow-providers-http/2.0.2rc1/ > https://pypi.org/project/apache-airflow-providers-docker/2.4.0rc1/ > https://pypi.org/project/apache-airflow-providers-google/6.3.0rc1/ > https://pypi.org/project/apache-airflow-providers-sftp/2.4.0rc1/ > https://pypi.org/project/apache-airflow-providers-jenkins/2.0.4rc1/ > https://pypi.org/project/apache-airflow-providers-microsoft-azure/3.5.0rc1/ > https://pypi.org/project/apache-airflow-providers-neo4j/2.1.0rc1/ > https://pypi.org/project/apache-airflow-providers-opsgenie/3.0.0rc1/ > https://pypi.org/project/apache-airflow-providers-imap/2.1.0rc1/ > https://pypi.org/project/apache-airflow-providers-facebook/2.2.0rc1/ > https://pypi.org/project/apache-airflow-providers-mongo/2.3.0rc1/ Cheers, J.
