This vote is cancelled. RC2 will follow

On Sun, Jan 26, 2025 at 12:30 AM Jarek Potiuk <ja...@potiuk.com> wrote:

> The PR is now merged so we can attempt to release an RC2
>
> On Fri, Jan 24, 2025 at 8:59 PM Jarek Potiuk <ja...@potiuk.com> wrote:
>
> > -1: (binding).
> >
> > I have found - during fixing my "move providers" PR (
> > https://github.com/apache/airflow/pull/45964) that I demoed my provider
> -
> > that celery provider (and few others) import "airflow.sdk". After
> > investigation it turned out that "task_sdk" package has not been removed
> > from the CI image when we run compatibility checks, so - accidentally -
> the
> > compatibility checks passed. After I fixed the CI to remove airflow_sdk
> in
> > compatibility checks - the compatibility tests started to fail:
> >
> https://github.com/apache/airflow/actions/runs/12956288364/job/36142514246?pr=45964#step:11:3005
> >
> > I am going to fix it as part of
> > https://github.com/apache/airflow/pull/45964
> >
> > Here is relevant import from celery_executor_utils.py
> >
> > ```
> > from airflow.executors.base_executor import BaseExecutor
> > from airflow.sdk.definitions._internal.dag_parsing_context import
> > ```
> >
> >
> > On Thu, Jan 23, 2025 at 10:18 AM Elad Kalif <elad...@apache.org> wrote:
> >
> >> Hey all,
> >>
> >> I have just cut the ad-hoc Airflow Celery provider package. This email
> is
> >> calling a vote on the release, which will last for 72 hours - which
> means
> >> that it will end on January 26, 2025 09:15 AM UTC and until 3 binding +1
> >> votes have been received.
> >>
> >> 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
> >> packages.
> >>
> >> *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_PROVIDER_PACKAGES.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_PROVIDER_PACKAGES.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/45957
> >>
> >> 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-celery/3.10.0rc1/
> >>
> >> Cheers,
> >> Elad Kalif
> >>
> >
>

Reply via email to