And to add to it: the "status" issue
https://github.com/apache/airflow/issues/35240 serves largely as the
"pre-release" changelog.

On Sat, Oct 28, 2023 at 9:11 PM Elad Kalif <elad...@apache.org> wrote:

> docs are published only after the vote is accepted and we release the
> packages.
> PR https://github.com/apache/airflow-site/pull/885 is handling the release
> of docs for the prepared packages
>
> On Sat, Oct 28, 2023 at 10:07 PM utkarsh sharma <utkarshar...@gmail.com>
> wrote:
>
> > Hey Elad,
> >
> > I wanted to see the change logs but I guess the following links are
> broken
> > for multiple packages, there could be something wrong with the pypi.org
> > page.
> > -
> >
> >
> https://airflow.apache.org/docs/apache-airflow-providers-apache-spark/4.3.0/changelog.html
> >
> > -
> >
> >
> https://airflow.apache.org/docs/apache-airflow-providers-apache-spark/4.3.0rc1/changelog.html
> >
> > Is there any other way I can check this?
> >
> > Thanks,
> > Utkarsh Sharma
> >
> > On Sat, Oct 28, 2023 at 11:25 PM Elad Kalif <elad...@apache.org> 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 October
> > 31,
> > > 2023 17:50 PM 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/35240
> > >
> > > You can find packages as well as detailed changelog following the below
> > > links:
> > >
> > > https://pypi.org/project/apache-airflow-providers-amazon/8.10.0rc1/
> > >
> https://pypi.org/project/apache-airflow-providers-apache-spark/4.3.0rc1/
> > >
> >
> https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/7.8.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-common-io/1.0.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-databricks/4.7.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-google/10.11.0rc1/
> > >
> >
> https://pypi.org/project/apache-airflow-providers-microsoft-azure/8.1.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-mongo/3.4.0rc1/
> > >
> https://pypi.org/project/apache-airflow-providers-openlineage/1.2.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-presto/5.2.1rc1/
> > > https://pypi.org/project/apache-airflow-providers-slack/8.3.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-smtp/1.4.1rc1/
> > > https://pypi.org/project/apache-airflow-providers-ssh/3.8.1rc1/
> > >
> > > Cheers,
> > > Elad Kalif
> > >
> >
>

Reply via email to