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 as well.
Thanks,
Mark
On 7/20/20, 9:39 AM, "Jacob Barrett" <jabarr...@vmware.com> wrote:
Alternatively, why not abandon 1.13 and try again with 1.14?
> On Jul 20, 2020, at 9:21 AM, Alexander Murmann <amurm...@apache.org>
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 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 postpone cutting the 1.14 release till we've actually
> shipped 1.13. Once we've shipped 1.13, we should have another conversation
> about timing of 1.14. I know the 1.13 release has been taxing on many
> people in our community and we might want to consider giving ourselves a
> little bit of a gap between releases.
