You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Jarek Potiuk <ja...@potiuk.com> on 2026/03/03 16:01:55 UTC
[ACCELERATED VOTE] Airflow Providers, release preparation date 2026-03-03
Hey all,
I have just cut the new wave Airflow Providers packages with release
preparation date 2026-03-03. This email is calling a vote on the release,
which will last for 24 hours - which means that it will end on Tuesday
March 04, 2026 15:59 PM UTC and until 3 binding +1 votes have been received.
This is a shortened (24 hours vote) as agreed by policy set it
https://lists.apache.org/thread/cv194w1fqqykrhswhmm54zy9gnnv6kgm
Consider this my (binding) +1.
Those are ad-hoc releases of edge3 amazon elasticsearch celery
informatica. providers - all of which had some regresions discovered or
release issues in the last wave.
Airflow Providers are available at:
https://dist.apache.org/repos/dist/dev/airflow/providers/2026-03-03
*apache-airflow-providers-2026-03-03-source.tar.gz* is the full source
tarball of airflow repo - snapshot taken at the moment of provider's
release.
*apache-airflow-providers-<PROVIDER>-*.tar.gz* are the convenience python
"sdist" distributions that we publish in PyPI
*apache_airflow_providers_<PROVIDER>-*.whl are the convenience Python
"wheel" distributions that we publish in PyPI.
The test procedure for PMC members is described in
https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.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_PROVIDERS.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 it.
The status of testing the providers by the community is kept here:
https://github.com/apache/airflow/issues/62794
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/9.22.0rc3/
https://pypi.org/project/apache-airflow-providers-celery/3.17.0rc2/
https://pypi.org/project/apache-airflow-providers-edge3/3.1.0rc2/
https://pypi.org/project/apache-airflow-providers-elasticsearch/6.5.0rc3/
https://pypi.org/project/apache-airflow-providers-informatica/0.1.1rc1/
Cheers,
Jarek Potiuk
Re: [ACCELERATED VOTE] Airflow Providers, release preparation date 2026-03-03
Posted by Dheeraj Turaga <dh...@gmail.com>.
+1 (non-binding)
Tested edge3 with 3.1.7 . Everything looks good!
On Tue, Mar 3, 2026 at 2:21 PM Vincent Beck <vi...@apache.org> wrote:
> +1 binding. Checked:
>
> * SVN
> * Reproducible package builds
> * Licence
> * Signature
> * SHA512
>
> On 2026/03/03 20:09:22 Buğra Öztürk wrote:
> > +1 binding. I have checked,
> > - SVN
> > - In Docker installation
> > - Reproducible package builds
> > - Licence
> > - Signature
> > - SHA512
> >
> > On Tue, Mar 3, 2026 at 5:02 PM Jarek Potiuk <ja...@potiuk.com> wrote:
> >
> > > Hey all,
> > >
> > > I have just cut the new wave Airflow Providers packages with release
> > > preparation date 2026-03-03. This email is calling a vote on the
> release,
> > > which will last for 24 hours - which means that it will end on Tuesday
> > > March 04, 2026 15:59 PM UTC and until 3 binding +1 votes have been
> > > received.
> > > This is a shortened (24 hours vote) as agreed by policy set it
> > > https://lists.apache.org/thread/cv194w1fqqykrhswhmm54zy9gnnv6kgm
> > >
> > > Consider this my (binding) +1.
> > >
> > > Those are ad-hoc releases of edge3 amazon elasticsearch celery
> > > informatica. providers - all of which had some regresions discovered or
> > > release issues in the last wave.
> > >
> > > Airflow Providers are available at:
> > > https://dist.apache.org/repos/dist/dev/airflow/providers/2026-03-03
> > >
> > > *apache-airflow-providers-2026-03-03-source.tar.gz* is the full source
> > > tarball of airflow repo - snapshot taken at the moment of provider's
> > > release.
> > >
> > > *apache-airflow-providers-<PROVIDER>-*.tar.gz* are the convenience
> python
> > > "sdist" distributions that we publish in PyPI
> > >
> > > *apache_airflow_providers_<PROVIDER>-*.whl are the convenience Python
> > > "wheel" distributions that we publish in PyPI.
> > >
> > > The test procedure for PMC members is described in
> > >
> > >
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.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_PROVIDERS.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 it.
> > >
> > > The status of testing the providers by the community is kept here:
> > > https://github.com/apache/airflow/issues/62794
> > >
> > > 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/9.22.0rc3/
> > >
> > > https://pypi.org/project/apache-airflow-providers-celery/3.17.0rc2/
> > >
> > > https://pypi.org/project/apache-airflow-providers-edge3/3.1.0rc2/
> > >
> > >
> https://pypi.org/project/apache-airflow-providers-elasticsearch/6.5.0rc3/
> > >
> > >
> https://pypi.org/project/apache-airflow-providers-informatica/0.1.1rc1/
> > >
> > >
> > > Cheers,
> > > Jarek Potiuk
> > >
> >
> >
> > --
> > Bugra Ozturk
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> For additional commands, e-mail: dev-help@airflow.apache.org
>
>
Re: [ACCELERATED VOTE] Airflow Providers, release preparation date 2026-03-03
Posted by Vincent Beck <vi...@apache.org>.
+1 binding. Checked:
* SVN
* Reproducible package builds
* Licence
* Signature
* SHA512
On 2026/03/03 20:09:22 Buğra Öztürk wrote:
> +1 binding. I have checked,
> - SVN
> - In Docker installation
> - Reproducible package builds
> - Licence
> - Signature
> - SHA512
>
> On Tue, Mar 3, 2026 at 5:02 PM Jarek Potiuk <ja...@potiuk.com> wrote:
>
> > Hey all,
> >
> > I have just cut the new wave Airflow Providers packages with release
> > preparation date 2026-03-03. This email is calling a vote on the release,
> > which will last for 24 hours - which means that it will end on Tuesday
> > March 04, 2026 15:59 PM UTC and until 3 binding +1 votes have been
> > received.
> > This is a shortened (24 hours vote) as agreed by policy set it
> > https://lists.apache.org/thread/cv194w1fqqykrhswhmm54zy9gnnv6kgm
> >
> > Consider this my (binding) +1.
> >
> > Those are ad-hoc releases of edge3 amazon elasticsearch celery
> > informatica. providers - all of which had some regresions discovered or
> > release issues in the last wave.
> >
> > Airflow Providers are available at:
> > https://dist.apache.org/repos/dist/dev/airflow/providers/2026-03-03
> >
> > *apache-airflow-providers-2026-03-03-source.tar.gz* is the full source
> > tarball of airflow repo - snapshot taken at the moment of provider's
> > release.
> >
> > *apache-airflow-providers-<PROVIDER>-*.tar.gz* are the convenience python
> > "sdist" distributions that we publish in PyPI
> >
> > *apache_airflow_providers_<PROVIDER>-*.whl are the convenience Python
> > "wheel" distributions that we publish in PyPI.
> >
> > The test procedure for PMC members is described in
> >
> > https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.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_PROVIDERS.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 it.
> >
> > The status of testing the providers by the community is kept here:
> > https://github.com/apache/airflow/issues/62794
> >
> > 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/9.22.0rc3/
> >
> > https://pypi.org/project/apache-airflow-providers-celery/3.17.0rc2/
> >
> > https://pypi.org/project/apache-airflow-providers-edge3/3.1.0rc2/
> >
> > https://pypi.org/project/apache-airflow-providers-elasticsearch/6.5.0rc3/
> >
> > https://pypi.org/project/apache-airflow-providers-informatica/0.1.1rc1/
> >
> >
> > Cheers,
> > Jarek Potiuk
> >
>
>
> --
> Bugra Ozturk
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
For additional commands, e-mail: dev-help@airflow.apache.org
Re: [ACCELERATED VOTE] Airflow Providers, release preparation date 2026-03-03
Posted by Buğra Öztürk <oz...@gmail.com>.
+1 binding. I have checked,
- SVN
- In Docker installation
- Reproducible package builds
- Licence
- Signature
- SHA512
On Tue, Mar 3, 2026 at 5:02 PM Jarek Potiuk <ja...@potiuk.com> wrote:
> Hey all,
>
> I have just cut the new wave Airflow Providers packages with release
> preparation date 2026-03-03. This email is calling a vote on the release,
> which will last for 24 hours - which means that it will end on Tuesday
> March 04, 2026 15:59 PM UTC and until 3 binding +1 votes have been
> received.
> This is a shortened (24 hours vote) as agreed by policy set it
> https://lists.apache.org/thread/cv194w1fqqykrhswhmm54zy9gnnv6kgm
>
> Consider this my (binding) +1.
>
> Those are ad-hoc releases of edge3 amazon elasticsearch celery
> informatica. providers - all of which had some regresions discovered or
> release issues in the last wave.
>
> Airflow Providers are available at:
> https://dist.apache.org/repos/dist/dev/airflow/providers/2026-03-03
>
> *apache-airflow-providers-2026-03-03-source.tar.gz* is the full source
> tarball of airflow repo - snapshot taken at the moment of provider's
> release.
>
> *apache-airflow-providers-<PROVIDER>-*.tar.gz* are the convenience python
> "sdist" distributions that we publish in PyPI
>
> *apache_airflow_providers_<PROVIDER>-*.whl are the convenience Python
> "wheel" distributions that we publish in PyPI.
>
> The test procedure for PMC members is described in
>
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.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_PROVIDERS.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 it.
>
> The status of testing the providers by the community is kept here:
> https://github.com/apache/airflow/issues/62794
>
> 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/9.22.0rc3/
>
> https://pypi.org/project/apache-airflow-providers-celery/3.17.0rc2/
>
> https://pypi.org/project/apache-airflow-providers-edge3/3.1.0rc2/
>
> https://pypi.org/project/apache-airflow-providers-elasticsearch/6.5.0rc3/
>
> https://pypi.org/project/apache-airflow-providers-informatica/0.1.1rc1/
>
>
> Cheers,
> Jarek Potiuk
>
--
Bugra Ozturk