Hi Simon- I think maybe we are seeing the severity of these bugs differently. There are three substantial issues addressed by this patch. While they don't affect many users, they do prevent KiCad from being used for larger, more complex boards that we nominally support. This is a also regression from v4.
I don't think that this is a "do we fix?" issue but rather a "how do we fix?" one. -S Am Fr., 1. Juni 2018 um 10:57 Uhr schrieb Simon Richter < [email protected]>: > Hi, > > On 01.06.2018 06:36, Seth Hillbrand wrote: > > > Do people have concerns with the risk exposure for this patch or would > > anyone like some additional time to evaluate? > > I think this needs a round of user testing, and doing it this late in > the 5.0 cycle (post rc2) would delay the release. > > If we're going to have 5.x minor releases, that would be a better > target. We now have two changes that need extensive testing but should > not behave semantics: > > - gtk3 > - connectivity speedup > > How this is mapped to releases is up to Wayne, I think. We could have a > 5.1 with both features (so we have to ask only once for testing), or > have one in 5.1, one in 5.2 (so testing is more focused). > > Simon > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
