The release candidates would be a good idea if we think anyone would test them. The failure mode would be if all those willing to take the risk were only willing to take it in order to see the next major version (ie: were running the master nightlies).
Another option would be to only back-port critical (and perhaps high) priority bugs to the dot-release branches…. > On 2 Aug 2019, at 13:05, Wayne Stambaugh <stambau...@gmail.com> wrote: > > Looks like we will be forgoing a 5.1.3 release and jumping to 5.1.4. > This bug is a definite show stopper. We need to do a better job of > testing fixes before we merge them into the 5.1 branch. Maybe we need > to start doing release candidates on the stable branch before releasing > buggy bug fixes? For those packagers who are providing 5.1.3 for > distos, I would avoid releasing it. > > Cheers, > > Wayne > > > On 8/2/19 2:33 PM, jp charras wrote: >> Hi Wayne, >> >> If the 5.1.3 is built from tag 5.1.3 (jul 25) version, there is a very >> annoying bug: >> Bug #1838446 >> >> This bug was fixed the Jul 31. >> >> This bug make impossible updating footprints, both from the dialog and >> from schematic, because the new footprint is not at the right place (the >> old footprint coordinate) but it is placed at the mouse cursor location. >> >> > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
