Current schedule for cutting support branches is:
Aug 3, 2020: cut support/1.14
Nov 2, 2020: cut support/1.15
Feb 1, 2021: cut support/1.16
May 3, 2021: cut support/1.17
I have a hard time understanding how anyone can trust that our schedule is
"time-based" if we can change the dates at the last
Hi Owen,
I am not proposing to abandon our time-based releases. It's unprecedented
for one of our releases to take this long. Even if we were to cut the
release now, it would likely not receive any attention till 1.13 is out. So
I don't think there is any benefit in cutting the release now. In add
The Geode community adopted a time-based quarterly cadence two years ago in the
hope it would lead to higher stability and more predictable releases. The idea
was that by knowing exactly when a branch cut is upcoming, developers will hold
off on high-risk changes and focus more on hardening as
I think re-cutting 1.13 from current develop is interesting, but I think I
agree with Donal that the amount of additional risk might not be worth it.
Geode 1.13 already has some cool new features like SNI support that I
believe some users have been waiting for and I'd hate to not get that out
for a
+1 to postponing 1.14.
Given the limited resources we have in terms of people who shepherd the release
process and ensure the quality of what we end up releasing, it would put an
unsustainable amount of strain on those who have already been working extremely
hard on getting 1.13 finished if we
Playing devil's advocate here, but I think the reason we would not like to move
to 1.14 would be that we have a ton testing already in to quantify issues on
1.13 and 1.14 would be (a bit) of an unknown quantity. Further, the core issues
that we are waiting on for 1.13 are presumable 1.14 issues
Alternatively, why not abandon 1.13 and try again with 1.14?
> On Jul 20, 2020, at 9:21 AM, Alexander Murmann wrote:
>
> Hi everyone,
>
> TL;DR: Let's discuss 1.14 once 1.13 is out.
>
> If we stick to our cadence of cutting a release every 3 months and shipping
> it 1 month later, 1.14 is due
Hi everyone,
TL;DR: Let's discuss 1.14 once 1.13 is out.
If we stick to our cadence of cutting a release every 3 months and shipping
it 1 month later, 1.14 is due to be cut two weeks from today. However, we
haven't shipped 1.13 yet and are still struggling with some issues.
I suggest that we pos
