+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).
I agree that having to wait another 72 hours can be a little annoying.
I like Jarek idea of an incompressible 24h window if the previous RC was
close to an end. This feels like a good compromise and also leave people
some time to do further testing in case the highlighted bug is tied to
other issu
24 hours seems reasonable for follow ups to me. The argument I could see for
keeping the 72 hours is that 72 hours means a decision would never be made over
a weekend. That may not be a terrible idea to keep, but I'd say if the initial
time is still 72 hours and revisions are only adding to th
> It is tempting to speed it up, more, but we've been already called out by the
> ASF board by rushing a release when it was not really justified (when we
> released 1.10.8
FYI if a similar situation happens with a future release of Airflow is that pip
fully respects yanking now, compared to wh
A bug was found in rc2 that'll necessitate an rc3. I'm canceling this vote
and will create 2.5.0rc3 soon.
On Tue, 29 Nov 2022 at 09:43, Jarek Potiuk wrote:
> +1 (binding) . Verified licences, signatures, checksums. I tested a
> few DAGs, looked around the new small UI improvements.
>
> I parti
Good point. The SHOULD is there and after discussions with the ASF
folks on JIRAs and members@a.o list - if there is a good reason, we
can shorten it. Critical security fix is definitely a good reason for
it (happened in Log4J for example) but the community (us) might decide
on releasing it earlie
To follw up on why I think this is a worth while to adopt:
It essentially comes down to attempting to reduce the workload and effort on
the release manager (which is already a pretty hidden and in someways thankless
job!)
When we discover a last minute bug like we did here it's quite stressful f
+1 to both (a) and (b) since RC2 up is usually a few commits
On 2022/11/30 09:47:26 Ash Berlin-Taylor wrote:
> Hi All,
>
> We've just had a case where a 11th hour bug on 2.5.0rc2 (well technically,
> 12:01 as the vote time had finished, but we hadn't closed it yet/wouldn't
> have released anywa
Hi All,
We've just had a case where a 11th hour bug on 2.5.0rc2 (well technically,
12:01 as the vote time had finished, but we hadn't closed it yet/wouldn't have
released anyway) https://github.com/apache/airflow/issues/28002.
The fix is easy (it's a two line change, plus a bit of tidy up) but w
