Yeah, something like that.
On Mon, 16 Mar 2020 at 12:57, Gabriel Beims Bräscher
wrote:
> Sounds like a plan.
>
> I guess that there would be a VOTE/testing round addressing 4.13.1 and
> then, once 4.13.1 is released, another VOTE/test round for 4.14.
>
> Em sáb., 14 de mar. de 2020 às 06:41, Wid
Sounds like a plan.
I guess that there would be a VOTE/testing round addressing 4.13.1 and
then, once 4.13.1 is released, another VOTE/test round for 4.14.
Em sáb., 14 de mar. de 2020 às 06:41, Wido den Hollander
escreveu:
>
>
> On 3/13/20 1:05 PM, Andrija Panic wrote:
> > Hi all,
> >
> > in or
On 3/13/20 1:05 PM, Andrija Panic wrote:
> Hi all,
>
> in order to avoid potential issues around upgrading 4.13.1.0 to 4.14.0.0 in
> future (if we release 4.13.1.0 after 4.14.0.0), I would like to see what
> the community thinks about us doing both releases at the same time?
>
> The reason for
Let's do it!
Regards,
Rohit Yadav
Software Architect, ShapeBlue
https://www.shapeblue.com
From: Andrija Panic
Sent: Friday, March 13, 2020 17:35
To: dev
Subject: "[DISCUSS] 4.13.1 at the same time with 4.14"
Hi all,
in order to avoid p
Hi all,
in order to avoid potential issues around upgrading 4.13.1.0 to 4.14.0.0 in
future (if we release 4.13.1.0 after 4.14.0.0), I would like to see what
the community thinks about us doing both releases at the same time?
The reason for asking is not just "yeah, great, let's do it" but the rea
