<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><div style="direction: inherit;"> </div> Sent from my iPhone...</div><div> On Sep 17, 2016, at 21:43, Keith Packard <<a href="mailto:keithp@keithp.com">keithp@keithp.com</a>> wrote: </div><blockquote type="cite"><div>Jeremy Huddleston Sequoia <<a href="mailto:jeremyhu@apple.com">jeremyhu@apple.com</a>> writes: <blockquote type="cite">[ Unknown signature status ] </blockquote><blockquote type="cite"> </blockquote><blockquote type="cite"><blockquote type="cite">On Sep 16, 2016, at 13:57, Keith Packard <<a href="mailto:keithp@keithp.com">keithp@keithp.com</a>> wrote: </blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> </blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> </blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I think we're ready for RC1 at this point, but wanted to give people a </blockquote></blockquote><blockquote type="cite"><blockquote type="cite">chance to scream about "just one more API change" until tomorrow. Let me </blockquote></blockquote><blockquote type="cite"><blockquote type="cite">know if there's something I'm missing; if I don't hear anything, I'll be </blockquote></blockquote><blockquote type="cite"><blockquote type="cite">tagging RC1 in the morning. </blockquote></blockquote><blockquote type="cite"> </blockquote><blockquote type="cite">IMO, we're not quite RC quality on master, so tagging it that way </blockquote><blockquote type="cite">feels a bit premature. </blockquote> And I didn't, I just set it to 99.2, which is a post-1.18, but pre-RC1 tag in our scheme (I think). <blockquote type="cite">ASan trips over a bunch of issues still. I'd like to land the patches </blockquote><blockquote type="cite">that I sent out over the weekend that address memory corruption issues </blockquote><blockquote type="cite">if the server is started without any screens attached. That issue was </blockquote><blockquote type="cite">made obvious due to the input thread changes which altered our </blockquote><blockquote type="cite">initialization order to reveal the issue. </blockquote> <blockquote type="cite">We should also address the use-after-free in CloseDownClient that I </blockquote><blockquote type="cite">discussed in <a href="https://bugs.freedesktop.org/show_bug.cgi?id=97770">https://bugs.freedesktop.org/show_bug.cgi?id=97770</a> and </blockquote><blockquote type="cite">figure out what's causing replies to get stuck unsent in the first </blockquote><blockquote type="cite">place (cf 9/11: Re: XLoadQueryFont() not returning with recent xserver </blockquote><blockquote type="cite">master). </blockquote> RC1 means we've got the feature set we want, but there may still be bugs. Do you have any features you'd like to land for 1.19 which haven't made it yet? Do you think there are bugs sufficient to jeopardize the 1.19 schedule? </div></blockquote><div style="direction: inherit;"> </div><div style="direction: inherit;">No features on my end. I've basically just been keeping XQuartz in maintenance mode, so no qualms with the API or Feature Freeze. I'd just like to try to get some of these bugs that I noticed squashed before the rc1 tag if possible.</div><div style="direction: inherit;"> </div><blockquote type="cite"><div><div style="direction: inherit;"> </div>-- -keith </div></blockquote></body></html>