Fwd: Analyst questions regarding Apache Airflow

2025-04-08 Thread Brian Proffitt
Any response for this?

BKP


Brian Proffitt
VP, Marketing & Publicity
VP, Conferences


-- Forwarded message -
From: Brian Proffitt 
Date: Wed, Mar 26, 2025 at 5:46 PM
Subject: Re: Analyst questions regarding Apache Airflow
To: Thierry Carrez , Allison Price <
alli...@openinfra.dev>
Cc: Ruth Suehle 


Airflow team:

If you haven't worked with analysts before, know that the research will not
likely be public and should only be available for a fee (though sometimes
analysts give them to nonprofits/OSS projects for free; it depends). The
benefit of participating is so that any end users who read the report get
to see the outcomes.

The downside to talking to any analyst is that a project might not show up
positively in the report versus its competitors, so it's helpful to find
out who else Forrester's looking at, so you all can decide if you want to
participate.

BKP

Brian Proffitt
VP, Marketing & Publicity
VP, Conferences


On Tue, Mar 25, 2025 at 3:03 PM Meg Bellavance 
wrote:

> Hello all,
>
> I'm working with Naveen on this research, and I wanted to send over the
> premise doc which includes more details on our Workload/Bath Automation
> research. I've attached it to this email.
>
> Best,
>
> Meg
>
>
>
>
> *Meg Bellavance (She | Her)*
> Research Associate  - Tech Architecture And Delivery
> mbellava...@forrester.com
> Forrester Research, Inc.
> 60 Acorn Park Drive, Cambridge, MA 02140 United States
> Forrester.com 
>
> --
> *From:* Brian Proffitt 
> *Sent:* Tuesday, March 25, 2025 1:58 PM
> *To:* Naveen Chhabra 
> *Cc:* Thierry Carrez ; Renee Taylor-Huot <
> retay...@forrester.com>; Meg Bellavance ;
> Allison Price 
> *Subject:* Re: Analyst questions regarding Apache Airflow
>
> That's odd, nothing shows up in the moderator queue from Forrester. That
> said, Naveen it's a pleasure to connect with you, how can I help?
>
> BKP
>
>
> Brian Proffitt
> VP, Marketing & Publicity
> VP, Conferences
>
>
> On Tue, Mar 25, 2025 at 1:48 PM Ruth Suehle  wrote:
>
> Sorry you didn't get a reply there! Copying Brian, who can help.
>
> On Tue, Mar 25, 2025, 1:02 PM Thierry Carrez 
> wrote:
>
> Hi Ruth,
>
> With my OpenInfra hat on, I have been in contact with Naveen Chhabra at
> Forrester. They were interested to get in touch with Apache Airflow
> folks for a research project they have been working on. They tried
> pr...@apache.org but were unsuccessful getting a connection through there.
>
> I was wondering if you could help and redirect them to someone at Apache
> Airflow that may be able to field their questions?
>
> Regards,
>
> --
> Thierry
>
>


Re: [VOTE] Airflow Providers prepared on April 06, 2025

2025-04-08 Thread Elad Kalif
common.messaging and fab are excluded from this vote

On Mon, Apr 7, 2025 at 9:22 AM Amogh Desai  wrote:

> +1 non binding.
>
> Tested my changes which primarily lied in these buckets:
>
> CI / static check fixes:
> - https://github.com/apache/airflow/pull/48671
> - https://github.com/apache/airflow/pull/48666
> - https://github.com/apache/airflow/pull/48808
>
> Actual changes
> - https://github.com/apache/airflow/pull/48826
> - https://github.com/apache/airflow/pull/46231
> - https://github.com/apache/airflow/pull/48683
>
> Ran this as well as a couple of test dags and all seem to work as expected.
>
> Thanks & Regards,
> Amogh Desai
>
>
> On Mon, Apr 7, 2025 at 7:54 AM Vishnu Chilukoori <
> vish.chiluko...@gmail.com>
> wrote:
>
> > +1 non-binding
> >
> > --
> > Regards,
> > Vishnu. Chilukoori
> >
> > On Sun, Apr 6, 2025 at 12:02 PM Pankaj Koti
> >  wrote:
> >
> > > +1 non-binding
> > >
> > > Tested my PR in the Databricks provider, it's included in the RC and
> the
> > > changes run as expected. Thanks for the release efforts!
> > >
> > > On Sun, Apr 6, 2025 at 9:50 PM Jarek Potiuk  wrote:
> > >
> > > > Good observation Jens Last time (RC) I removed the node_modules
> > manually
> > > -
> > > > had no time to fix it, so I guess we should cancel this one and
> release
> > > the
> > > > next one. I will add a fix shortly.
> > > >
> > > > On Sun, Apr 6, 2025 at 5:49 PM Jens Scheffler
> >  > > >
> > > > wrote:
> > > >
> > > > > Hi Elad,
> > > > >
> > > > > thanks for preparing! Hope we make Edge to be published as well
> soon.
> > > > >
> > > > > For all (including edge even though not published atm) providers
> > > > > *except* FAB
> > > > >
> > > > > +1 (binding) - Checked SVN, Check in Docker, Reproducible package
> > > build,
> > > > > Licenses, Signatures
> > > > >
> > > > > On FAB I saw a difference, the folder
> > > > > |src/airflow/providers/fab/www/node_modules was packages into the
> > > > > release (+21MB) which I assume is a temporary folder as being in
> > > > > .gitignore. Was not able to re-produce the same binary (difference:
> > the
> > > > > node_modules only, all other looked good). So until clarified -
> > assume
> > > > > this needs to be cleaned, I'd -1 for FAB. I assume this is due to
> > first
> > > > > "real" release with the changed structures.|
> > > > >
> > > > > |Jens
> > > > > |
> > > > >
> > > > > On 06.04.25 11:02, 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 72 hours - which means that it will end on
> > April
> > > > 09,
> > > > > > 2025 09:00 AM UTC and until 3 binding +1 votes have been
> received.
> > > > > >
> > > > > > Consider this my (binding) +1.
> > > > > >
> > > > > > Provider edge was not cut due tohttps://
> > > > > github.com/pypi/support/issues/5829
> > > > > >
> > > > > > Airflow Providers are available at:
> > > > > > https://dist.apache.org/repos/dist/dev/airflow/providers/
> > > > > >
> > > > > > *apache-airflow-providers--*.tar.gz* are the binary
> > > > > >   Python "sdist" release - they are also official "sources" for
> the
> > > > > Provider
> > > > > > distributions.
> > > > > >
> > > > > > *apache_airflow_providers_-*.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/48842
> > > > > >
> > > > > > 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
> > > > >

Re: Analyst questions regarding Apache Airflow

2025-04-08 Thread Jarek Potiuk
Hey Brian,

I believe the devlist has not been copied in your previous email which was
apparently addressed to us (see the to: list there) - I could not find it
in the devlist in the past as well
https://lists.apache.org/list?dev@airflow.apache.org:lte=1M:Analyst%20questions%20regarding%20Apache%20Airflow
.

Could you send us the original email with the questions so that we know
what it is about ?

J.

On Tue, Apr 8, 2025 at 9:17 AM Brian Proffitt  wrote:

> Any response for this?
>
> BKP
>
>
> Brian Proffitt
> VP, Marketing & Publicity
> VP, Conferences
>
>
> -- Forwarded message -
> From: Brian Proffitt 
> Date: Wed, Mar 26, 2025 at 5:46 PM
> Subject: Re: Analyst questions regarding Apache Airflow
> To: Thierry Carrez , Allison Price <
> alli...@openinfra.dev>
> Cc: Ruth Suehle 
>
>
> Airflow team:
>
> If you haven't worked with analysts before, know that the research will not
> likely be public and should only be available for a fee (though sometimes
> analysts give them to nonprofits/OSS projects for free; it depends). The
> benefit of participating is so that any end users who read the report get
> to see the outcomes.
>
> The downside to talking to any analyst is that a project might not show up
> positively in the report versus its competitors, so it's helpful to find
> out who else Forrester's looking at, so you all can decide if you want to
> participate.
>
> BKP
>
> Brian Proffitt
> VP, Marketing & Publicity
> VP, Conferences
>
>
> On Tue, Mar 25, 2025 at 3:03 PM Meg Bellavance 
> wrote:
>
> > Hello all,
> >
> > I'm working with Naveen on this research, and I wanted to send over the
> > premise doc which includes more details on our Workload/Bath Automation
> > research. I've attached it to this email.
> >
> > Best,
> >
> > Meg
> >
> >
> >
> >
> > *Meg Bellavance (She | Her)*
> > Research Associate  - Tech Architecture And Delivery
> > mbellava...@forrester.com
> > Forrester Research, Inc.
> > 60 Acorn Park Drive, Cambridge, MA 02140 United States
> > Forrester.com 
> >
> > --
> > *From:* Brian Proffitt 
> > *Sent:* Tuesday, March 25, 2025 1:58 PM
> > *To:* Naveen Chhabra 
> > *Cc:* Thierry Carrez ; Renee Taylor-Huot <
> > retay...@forrester.com>; Meg Bellavance ;
> > Allison Price 
> > *Subject:* Re: Analyst questions regarding Apache Airflow
> >
> > That's odd, nothing shows up in the moderator queue from Forrester. That
> > said, Naveen it's a pleasure to connect with you, how can I help?
> >
> > BKP
> >
> >
> > Brian Proffitt
> > VP, Marketing & Publicity
> > VP, Conferences
> >
> >
> > On Tue, Mar 25, 2025 at 1:48 PM Ruth Suehle  wrote:
> >
> > Sorry you didn't get a reply there! Copying Brian, who can help.
> >
> > On Tue, Mar 25, 2025, 1:02 PM Thierry Carrez 
> > wrote:
> >
> > Hi Ruth,
> >
> > With my OpenInfra hat on, I have been in contact with Naveen Chhabra at
> > Forrester. They were interested to get in touch with Apache Airflow
> > folks for a research project they have been working on. They tried
> > pr...@apache.org but were unsuccessful getting a connection through
> there.
> >
> > I was wondering if you could help and redirect them to someone at Apache
> > Airflow that may be able to field their questions?
> >
> > Regards,
> >
> > --
> > Thierry
> >
> >
>


Re: Analyst questions regarding Apache Airflow

2025-04-08 Thread Vikram Koka
Brian,

Adding to Jarek's response above, I am happy to engage with them and help
answer the questions.
Please let me know.

Vikram


On Tue, Apr 8, 2025 at 6:43 AM Jarek Potiuk  wrote:

> Hey Brian,
>
> I believe the devlist has not been copied in your previous email which was
> apparently addressed to us (see the to: list there) - I could not find it
> in the devlist in the past as well
>
> https://lists.apache.org/list?dev@airflow.apache.org:lte=1M:Analyst%20questions%20regarding%20Apache%20Airflow
> .
>
> Could you send us the original email with the questions so that we know
> what it is about ?
>
> J.
>
> On Tue, Apr 8, 2025 at 9:17 AM Brian Proffitt  wrote:
>
> > Any response for this?
> >
> > BKP
> >
> >
> > Brian Proffitt
> > VP, Marketing & Publicity
> > VP, Conferences
> >
> >
> > -- Forwarded message -
> > From: Brian Proffitt 
> > Date: Wed, Mar 26, 2025 at 5:46 PM
> > Subject: Re: Analyst questions regarding Apache Airflow
> > To: Thierry Carrez , Allison Price <
> > alli...@openinfra.dev>
> > Cc: Ruth Suehle 
> >
> >
> > Airflow team:
> >
> > If you haven't worked with analysts before, know that the research will
> not
> > likely be public and should only be available for a fee (though sometimes
> > analysts give them to nonprofits/OSS projects for free; it depends). The
> > benefit of participating is so that any end users who read the report get
> > to see the outcomes.
> >
> > The downside to talking to any analyst is that a project might not show
> up
> > positively in the report versus its competitors, so it's helpful to find
> > out who else Forrester's looking at, so you all can decide if you want to
> > participate.
> >
> > BKP
> >
> > Brian Proffitt
> > VP, Marketing & Publicity
> > VP, Conferences
> >
> >
> > On Tue, Mar 25, 2025 at 3:03 PM Meg Bellavance <
> mbellava...@forrester.com>
> > wrote:
> >
> > > Hello all,
> > >
> > > I'm working with Naveen on this research, and I wanted to send over the
> > > premise doc which includes more details on our Workload/Bath Automation
> > > research. I've attached it to this email.
> > >
> > > Best,
> > >
> > > Meg
> > >
> > >
> > >
> > >
> > > *Meg Bellavance (She | Her)*
> > > Research Associate  - Tech Architecture And Delivery
> > > mbellava...@forrester.com
> > > Forrester Research, Inc.
> > > 60 Acorn Park Drive, Cambridge, MA 02140 United States
> > > Forrester.com 
> > >
> > > --
> > > *From:* Brian Proffitt 
> > > *Sent:* Tuesday, March 25, 2025 1:58 PM
> > > *To:* Naveen Chhabra 
> > > *Cc:* Thierry Carrez ; Renee Taylor-Huot <
> > > retay...@forrester.com>; Meg Bellavance ;
> > > Allison Price 
> > > *Subject:* Re: Analyst questions regarding Apache Airflow
> > >
> > > That's odd, nothing shows up in the moderator queue from Forrester.
> That
> > > said, Naveen it's a pleasure to connect with you, how can I help?
> > >
> > > BKP
> > >
> > >
> > > Brian Proffitt
> > > VP, Marketing & Publicity
> > > VP, Conferences
> > >
> > >
> > > On Tue, Mar 25, 2025 at 1:48 PM Ruth Suehle  wrote:
> > >
> > > Sorry you didn't get a reply there! Copying Brian, who can help.
> > >
> > > On Tue, Mar 25, 2025, 1:02 PM Thierry Carrez 
> > > wrote:
> > >
> > > Hi Ruth,
> > >
> > > With my OpenInfra hat on, I have been in contact with Naveen Chhabra at
> > > Forrester. They were interested to get in touch with Apache Airflow
> > > folks for a research project they have been working on. They tried
> > > pr...@apache.org but were unsuccessful getting a connection through
> > there.
> > >
> > > I was wondering if you could help and redirect them to someone at
> Apache
> > > Airflow that may be able to field their questions?
> > >
> > > Regards,
> > >
> > > --
> > > Thierry
> > >
> > >
> >
>


Re: Au revoir Flask

2025-04-08 Thread Ferruzzi, Dennis
Great work, all.

> Yay! FABulous milestone!

I believe you mean FAB-u-less?  :P


 - ferruzzi



From: Abhishek Bhakat 
Sent: Monday, April 7, 2025 10:54 PM
To: dev@airflow.apache.org
Subject: RE: [EXT] Au revoir Flask

CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you can confirm the sender and know the 
content is safe.



AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe. Ne 
cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne pouvez pas 
confirmer l’identité de l’expéditeur et si vous n’êtes pas certain que le 
contenu ne présente aucun risque.



Yay! FABulous milestone!

On Tue, Apr 8, 2025 at 2:27 AM Amogh Desai  wrote:

> Awesome news Vincent!
>
> Thanks & Regards,
> Amogh Desai
>
>
> On Tue, Apr 8, 2025 at 6:58 AM Wei Lee  wrote:
>
> > This is nice!
> >
> > Best,
> > Wei
> >
> > > On Apr 8, 2025, at 3:35 AM, Vikram Koka 
> > wrote:
> > >
> > > Very cool!
> > >
> > > Great work here! Love the "FAB-light" state.
> > >
> > > On Mon, Apr 7, 2025 at 12:22 PM Jarek Potiuk  wrote:
> > >
> > >> Cool. We are now FAB-light (not yet FAB-less, but that's still a win).
> > >>
> > >> On Mon, Apr 7, 2025 at 3:11 PM Bishundeo, Rajeshwar
> > >>  wrote:
> > >>
> > >>> Wow. Major milestone in the history of Airflow. Great job Vincent,
> Jed,
> > >>> Jarek and everyone else involved!
> > >>>
> > >>> -- Rajesh
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> On 2025-04-07, 3:09 PM, "Beck, Vincent"  > >>> LID> wrote:
> > >>>
> > >>>
> > >>> CAUTION: This email originated from outside of the organization. Do
> not
> > >>> click links or open attachments unless you can confirm the sender and
> > >> know
> > >>> the content is safe.
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur
> > externe.
> > >>> Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne
> > >> pouvez
> > >>> pas confirmer l’identité de l’expéditeur et si vous n’êtes pas
> certain
> > >> que
> > >>> le contenu ne présente aucun risque.
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> Hi all,
> > >>>
> > >>>
> > >>> Just a quick FYI — PR #48457 (
> > >> https://github.com/apache/airflow/pull/48457
> > >>> ), which removes the
> > Flask
> > >>> AppBuilder (FAB) provider from the preinstalled providers, has just
> > been
> > >>> merged. This marks the successful completion of AIP-79! 🎉
> > >>>
> > >>>
> > >>> Going forward, unless you explicitly install the FAB provider as an
> > >> extra,
> > >>> Flask is no longer a core dependency of Airflow.
> > >>>
> > >>>
> > >>> Huge thanks to everyone who contributed along the way — with a
> special
> > >>> shout-out to Jarek for consistently providing help with questions and
> > >>> tricky issues, and of course to Jed, who initiated the AIP and put in
> > an
> > >>> immense amount of work to see it through.
> > >>>
> > >>>
> > >>>
> > >>> Thanks again to all involved!
> > >>>
> > >>>
> > >>> Vincent
> > >>>
> > >>>
> > >>>
> > >>>
> > >>
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> > For additional commands, e-mail: dev-h...@airflow.apache.org
> >
> >
>


Re: [VOTE] Airflow Providers prepared on April 06, 2025

2025-04-08 Thread Jarek Potiuk
+1 - binding - checked reproducibility (fab does not pass it), signatures,
checksums, licences, checked all my changes - except fab size and
reproducibility all is good.

On Tue, Apr 8, 2025 at 8:52 AM Elad Kalif  wrote:

> common.messaging and fab are excluded from this vote
>
> On Mon, Apr 7, 2025 at 9:22 AM Amogh Desai 
> wrote:
>
> > +1 non binding.
> >
> > Tested my changes which primarily lied in these buckets:
> >
> > CI / static check fixes:
> > - https://github.com/apache/airflow/pull/48671
> > - https://github.com/apache/airflow/pull/48666
> > - https://github.com/apache/airflow/pull/48808
> >
> > Actual changes
> > - https://github.com/apache/airflow/pull/48826
> > - https://github.com/apache/airflow/pull/46231
> > - https://github.com/apache/airflow/pull/48683
> >
> > Ran this as well as a couple of test dags and all seem to work as
> expected.
> >
> > Thanks & Regards,
> > Amogh Desai
> >
> >
> > On Mon, Apr 7, 2025 at 7:54 AM Vishnu Chilukoori <
> > vish.chiluko...@gmail.com>
> > wrote:
> >
> > > +1 non-binding
> > >
> > > --
> > > Regards,
> > > Vishnu. Chilukoori
> > >
> > > On Sun, Apr 6, 2025 at 12:02 PM Pankaj Koti
> > >  wrote:
> > >
> > > > +1 non-binding
> > > >
> > > > Tested my PR in the Databricks provider, it's included in the RC and
> > the
> > > > changes run as expected. Thanks for the release efforts!
> > > >
> > > > On Sun, Apr 6, 2025 at 9:50 PM Jarek Potiuk 
> wrote:
> > > >
> > > > > Good observation Jens Last time (RC) I removed the node_modules
> > > manually
> > > > -
> > > > > had no time to fix it, so I guess we should cancel this one and
> > release
> > > > the
> > > > > next one. I will add a fix shortly.
> > > > >
> > > > > On Sun, Apr 6, 2025 at 5:49 PM Jens Scheffler
> > >  > > > >
> > > > > wrote:
> > > > >
> > > > > > Hi Elad,
> > > > > >
> > > > > > thanks for preparing! Hope we make Edge to be published as well
> > soon.
> > > > > >
> > > > > > For all (including edge even though not published atm) providers
> > > > > > *except* FAB
> > > > > >
> > > > > > +1 (binding) - Checked SVN, Check in Docker, Reproducible package
> > > > build,
> > > > > > Licenses, Signatures
> > > > > >
> > > > > > On FAB I saw a difference, the folder
> > > > > > |src/airflow/providers/fab/www/node_modules was packages into the
> > > > > > release (+21MB) which I assume is a temporary folder as being in
> > > > > > .gitignore. Was not able to re-produce the same binary
> (difference:
> > > the
> > > > > > node_modules only, all other looked good). So until clarified -
> > > assume
> > > > > > this needs to be cleaned, I'd -1 for FAB. I assume this is due to
> > > first
> > > > > > "real" release with the changed structures.|
> > > > > >
> > > > > > |Jens
> > > > > > |
> > > > > >
> > > > > > On 06.04.25 11:02, 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 72 hours - which means that it will end on
> > > April
> > > > > 09,
> > > > > > > 2025 09:00 AM UTC and until 3 binding +1 votes have been
> > received.
> > > > > > >
> > > > > > > Consider this my (binding) +1.
> > > > > > >
> > > > > > > Provider edge was not cut due tohttps://
> > > > > > github.com/pypi/support/issues/5829
> > > > > > >
> > > > > > > Airflow Providers are available at:
> > > > > > > https://dist.apache.org/repos/dist/dev/airflow/providers/
> > > > > > >
> > > > > > > *apache-airflow-providers--*.tar.gz* are the binary
> > > > > > >   Python "sdist" release - they are also official "sources" for
> > the
> > > > > > Provider
> > > > > > > distributions.
> > > > > > >
> > > > > > > *apache_airflow_providers_-*.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