Re: [LAZY CONSENSUS] Allow shorter voting periods for subsequent RCs

2023-03-11 Thread Elad Kalif
à 21:29, Ferruzzi, Dennis > > a écrit : > > > +1 (non-bindingly lazy) > > > > > > > > From: Pierre Jeambrun > > Sent: Tuesday, March 7, 2023 12:11 PM > > To: dev@airflow.apache.org > > Subject: [EXT

Re: [LAZY CONSENSUS] Allow shorter voting periods for subsequent RCs

2023-03-10 Thread Pierre Jeambrun
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. Do not > click links or open attachments unless you can confirm the sender and know &

Re: [LAZY CONSENSUS] Allow shorter voting periods for subsequent RCs

2023-03-07 Thread Ferruzzi, Dennis
+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

[LAZY CONSENSUS] Allow shorter voting periods for subsequent RCs

2023-03-07 Thread Pierre Jeambrun
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 voting