+1 (non-binding). Checked files, install (using the newly updated pmc
Dockerfile :D), license and checksum.
From: Jarek Potiuk
Sent: Tuesday, March 7, 2023 1:53:26 PM
To: dev@airflow.apache.org
Subject: RE: [EXTERNAL][VOTE] Airflow Providers prepared on March
done
On Tue, Mar 7, 2023 at 7:56 AM person wrote:
>
> Hello,
>
> Writing in regards to this; "You will need to request edit access to the
> Confluence page in order to create your AIP document" may you grant me
> access?
>
> Email: thirdsea...@gmail.com
> Login: thirdseason
>
> Thanks kindly
+1 binding. Checks licence, signature, checksum.
On Tue, Mar 7, 2023 at 6:02 PM Kaxil Naik wrote:
>
> +1 binding
>
> On Tue, 7 Mar 2023 at 13:04, Hussein Awala wrote:
>
> > +1 (non-binding)
> >
> >
> > From: Elad Kalif
> > Sent: Tuesday, March 7, 2023 9:26:17
+1 (non-bindingly lazy)
From: Pierre Jeambrun
Sent: Tuesday, March 7, 2023 12:11 PM
To: dev@airflow.apache.org
Subject: [EXTERNAL] [LAZY CONSENSUS] Allow shorter voting periods for
subsequent RCs
CAUTION: This email originated from outside of the organization.
Hi all,
*Context:*Having a 72h vote window on each subsequent RCs can slow down the
release process, bring some annoyance and add load on the release manager.
This could be avoided, especially when the new RC only ships a few extra
commits. This proposal would bring some flexibility to the
I will start the lazy consensus tonight :)
On Tue 7 Mar 2023 at 18:02, Kaxil Naik wrote:
> +1
>
> On Tue, 7 Mar 2023 at 16:56, Jarek Potiuk wrote:
>
> > +1
> >
> > On Tue, Mar 7, 2023 at 1:11 PM Pierre Jeambrun
> > wrote:
> > >
> > > Hello,
> > >
> > > I don’t think we had a lazy consensus on
+1
On Tue, 7 Mar 2023 at 16:56, Jarek Potiuk wrote:
> +1
>
> On Tue, Mar 7, 2023 at 1:11 PM Pierre Jeambrun
> wrote:
> >
> > Hello,
> >
> > I don’t think we had a lazy consensus on this matter but we already
> applied
> > it a couple of times before (for 2.5.1 and another one before that, if I
+1 binding
On Tue, 7 Mar 2023 at 13:04, Hussein Awala wrote:
> +1 (non-binding)
>
>
> From: Elad Kalif
> Sent: Tuesday, March 7, 2023 9:26:17 AM
> To: dev@airflow.apache.org
> Subject: [VOTE] Airflow Providers prepared on March 07, 2023
>
> Hey all,I have just
+1
On Tue, Mar 7, 2023 at 1:11 PM Pierre Jeambrun wrote:
>
> Hello,
>
> I don’t think we had a lazy consensus on this matter but we already applied
> it a couple of times before (for 2.5.1 and another one before that, if I am
> not mistaken).
>
> I think it would be good to start a lazy
+1 (non-binding)
From: Elad Kalif
Sent: Tuesday, March 7, 2023 9:26:17 AM
To: dev@airflow.apache.org
Subject: [VOTE] Airflow Providers prepared on March 07, 2023
Hey all,I have just cut ad hoc release for Airflow Hashicorp Provider
package (RC2). This email is
Hello,
I don’t think we had a lazy consensus on this matter but we already applied
it a couple of times before (for 2.5.1 and another one before that, if I am
not mistaken).
I think it would be good to start a lazy consensus, just to follow the
standard protocol and have a record of this in our
Hey all,I have just cut ad hoc release for Airflow Hashicorp Provider
package (RC2). This email is calling a vote on the release, which will
last for 72 hours - which means that it will end on March 10, 2023
08:30 AM UTC
Consider this my (binding) +1.
Airflow Providers are available
12 matches
Mail list logo
