I agree with what Ash is proposing, and would like to give my +1. Thanks.
XD > On 7 Feb 2020, at 2:05 PM, Ash Berlin-Taylor <[email protected]> wrote: > > Hello all, > > So Werkzeug 1.0 was released this morning, and it finally broke a number of > direct or indirect dependencies of ours (Werkzeug is a WSGI helper library. > It mans "tool" in German.) -- meaning 1.10.8 that was just released won't > funciton > (The fix for now is to do pip install "werkzeug<1.0.0") > So I'm going to release 1.10.9 with the fix from Jarek to pin the version > (yes, pinning properly is something we still need to tackle.) and I would > like to not wait for 72 hours for this release. > It appears that 72 hours is just a convention, see > https://apache.org/legal/release-policy.html#release-approval: >> Release votes SHOULD remain open for at least 72 hours. > In this case since the change (https://github.com/apache/airflow/pull/7377) > is one line to restrict the version of Werkzeug to the known working version > that passed the 1.10.8 vote I am propsing that in case I have the following > vote: > For 72 hours _OR_ until 3 binding votes have been cast > (Normally the vote is and.) What do people thing? > -ash
