+1 On Tue, 7 Mar 2023 at 16:56, Jarek Potiuk <ja...@potiuk.com> wrote:
> +1 > > On Tue, Mar 7, 2023 at 1:11 PM Pierre Jeambrun <pierrejb...@gmail.com> > 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 consensus, just to follow the > > standard protocol and have a record of this in our archives. > > > > Best regards, > > Pierre > > > > On Tue 7 Mar 2023 at 08:27, Elad Kalif <elad...@apache.org> wrote: > > > > > Did we have a lazy consensus for this policy? I can't find the thread. > > > Wanted to see if I can apply the policy on hashicorp provider 3.3.0rc2 > but > > > since I can't find the policy thread I'll go with the 72 hours window. > > > > > > On Wed, Nov 30, 2022 at 11:59 PM Jed Cunningham < > jedcunning...@apache.org> > > > wrote: > > > > > > > +1 to shorter follow up RCs and +1 to a minimum of 24 hours on those > > > > follow ups (at the discretion of the release manager). > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org > For additional commands, e-mail: dev-h...@airflow.apache.org > >
