+1 (binding) - checked reproducibility, licences, checksums, signatures.
There is a small issue with .tar.gz reproducibility due to the way we
rushed with the release but .whl packages are fine and binary reproducible
and I checked that the difference comes only from slight difference in
description of changelogs - not a blocker for release.

On Sun, Apr 20, 2025 at 12:00 PM Jens Scheffler <j_scheff...@gmx.de.invalid>
wrote:

> +1 (binding) - Checked SVN, Check in Docker, Reproducible package build,
> Licenses, Signatures
>
> I tested Edge3 package in Airflow 2.10, main and 3.0.0rc4 with the
> "Integration Test" DAG from the edge3 package. Seems to be working well.
>
> Just I needed ot realize that we had never tested with FAB being removed
> in 3.0.0 before (at least I never did). If FAB is not installed the API
> endpoints fails to start, then edge is not working. Unfortunately FAB in
> Edge3 was modelled as an optional dependency until now. Opened PR #49473
> to make the dependency mandatory. In my view this does not block the
> release... but other opinions welcome.
>
> On 20.04.25 09:13, Elad Kalif 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 *24 hours* - which
> means
> > that it will end on April 21, 2025 07:05 AM 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
> > Due to the following reasons:
> > 1. The providers in the wave have no user impact till we release Airflow
> 3.
> > 2. These providers are already tested as part of Airflow3 rc3 as the code
> > was used from SVN.
> > 3. We must release these providers tomorrow to be able to build the final
> > Airflow 3 image.
> > 4. Release managers and PMC members are in alignment for this expedite
> vote.
> >
> > 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
> > distributions.
> >
> > *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_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.
> >
> > The status of testing the providers by the community is kept here:
> > https://github.com/apache/airflow/issues/49471
> >
> > 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-edge3/1.0.0rc2/
> > https://pypi.org/project/apache-airflow-providers-git/0.0.2rc3/
> >
> > 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