; the
> > > bigger/popular provider?
> > > >
> > > > As long as we are alright handling the potential issues like adults,
> > > then I think it's a solid idea. I've just seen too many groups of grown
> > > adults devolve into children when they perceive fa
> > > > I agree that we should exclude providers that block us.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Mar 28, 2023 at 9:58 PM Ferruzzi, Dennis
> > > > > mailto:ferru...@amazon.c
ny groups of grown
> adults devolve into children when they perceive favoritism or bias.
> >
> >
> > - ferruzzi
> >
> >
> >
> > From: Jarek Potiuk
> > Sent: Wednesday, March 29, 2023 11:06 AM
> > To: dev@airflow.apache.org
&g
iuk
> Sent: Wednesday, March 29, 2023 11:06 AM
> To: dev@airflow.apache.org
> Subject: RE: [EXTERNAL][DISCUSS] Exclude some providers that hold us back
> from releasing
>
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachment
: [EXTERNAL][DISCUSS] Exclude some providers that hold us back from
releasing
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.
I see a consensus building up :). So I
dating/upgrading it, correct?
> > >
> > >
> > > - ferruzzi
> > >
> > >
> > >
> > > From: Ash Berlin-Taylor mailto:a...@apache.org>>
> > > Sent: Tuesday, March 28, 2023 7:11 AM
> > > To
orrect?
> >
> >
> > - ferruzzi
> >
> >
> >
> > From: Ash Berlin-Taylor mailto:a...@apache.org>>
> > Sent: Tuesday, March 28, 2023 7:11 AM
> > To: dev@airflow.apache.org <mailto:dev@airflow.apache.org&g
<mailto:dev@airflow.apache.org>; Daniel Standish
> Subject: RE: [EXTERNAL][DISCUSS] Exclude some providers that hold us back
> from releasing
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you can confirm the se
ing that nobody is actively updating/upgrading it, correct?
> >
> >
> > - ferruzzi
> >
> >
> >
> > From: Ash Berlin-Taylor
> > Sent: Tuesday, March 28, 2023 7:11 AM
> > To: dev@airflow.apache.org; Daniel Standish
> > S
n
> indicating that nobody is actively updating/upgrading it, correct?
>
>
> - ferruzzi
>
>
>
> From: Ash Berlin-Taylor
> Sent: Tuesday, March 28, 2023 7:11 AM
> To: dev@airflow.apache.org; Daniel Standish
> Subject: RE: [EXTER
Sent: Tuesday, March 28, 2023 7:11 AM
To: dev@airflow.apache.org; Daniel Standish
Subject: RE: [EXTERNAL][DISCUSS] Exclude some providers that hold us back from
releasing
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you can confirm
Yeah agreed.
Each provider should be treated like a separate project/release - it's just
that we batch up releases to save time of the release manager.
-a
On 28 March 2023 07:05:13 BST, Daniel Standish
wrote:
>It seems reasonable to me.
>
>On Mon, Mar 27, 2023 at 12:02 AM Jarek Potiuk
It seems reasonable to me.
On Mon, Mar 27, 2023 at 12:02 AM Jarek Potiuk wrote:
> Hello Everyone,
>
> TL;DR; I wanted to raise a discussion and make a proposal about option
> to skip some niche providers of our from releasing if they are holding
> us back, regarding the dependencies
>
> We are
Hello Everyone,
TL;DR; I wanted to raise a discussion and make a proposal about option
to skip some niche providers of our from releasing if they are holding
us back, regarding the dependencies
We are going through some troubles with dependencies of our providers
- mostly around some outdated
14 matches
Mail list logo
