I'm fine with leaving them in nightly builds as well.
On 2/26/20 6:54 AM, Ian McInerney wrote:
> I think we should leave them in our Nightly builds. We don't seem to get
> too many issues reported with them, and they usually indicate something
> is wrong if they do trigger.
>
> -Ian
>
> On Wed,
I think we should leave them in our Nightly builds. We don't seem to get
too many issues reported with them, and they usually indicate something is
wrong if they do trigger.
-Ian
On Wed, 26 Feb 2020, 11:10 Jeff Young, wrote:
> I’d be inclined to leave them on for nightlies.
>
> That being said,
OK, I’m coming around to the idea of a hybrid system (tabs + outline + severity
filtering).
Jon, could you post your violation taxonomy here?
On the settings front, I do actually think they belong in a different dialog (a
la Allegro). But we could have a right-button menu though that takes you
I’d be inclined to leave them on for nightlies.
That being said, the signal-to-noise ratio on the reports we get is pretty low,
so I don’t feel strongly.
> On 26 Feb 2020, at 05:21, Adam Wolf wrote:
>
> Hi folks!
>
> Right now, wx debug/asserts are turned on for macOS nightly builds,
> but d
4 matches
Mail list logo
