Yeah, something like that. On Mon, 16 Mar 2020 at 12:57, Gabriel Beims Bräscher <gabrasc...@gmail.com> 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, Wido den Hollander <w...@widodh.nl> > escreveu: > >> >> >> 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 asking is not just "yeah, great, let's do it" but the >> reason >> > is that community would have to do double the TESTING effort for both >> > releases during the voting process, at pretty much the same time. >> >> I think that's a good idea. Mainly the databse upgrades are painful and >> this makes it a lot easier. >> >> We then have to merge a couple of things for 4.13.1 then :-) >> >> We should prevent dragging the releases even further. >> >> Wido >> >> > >> > Opinion? >> > >> > Thanks, >> > >> > -- Andrija Panić
