Sent from my iPhone...

> On Sep 17, 2016, at 21:43, Keith Packard <> wrote:
> Jeremy Huddleston Sequoia <> writes:
>> [ Unknown signature status ]
>>> On Sep 16, 2016, at 13:57, Keith Packard <> wrote:
>>> I think we're ready for RC1 at this point, but wanted to give people a
>>> chance to scream about "just one more API change" until tomorrow. Let me
>>> know if there's something I'm missing; if I don't hear anything, I'll be
>>> tagging RC1 in the morning.
>> IMO, we're not quite RC quality on master, so tagging it that way
>> feels a bit premature.
> 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).
>> ASan trips over a bunch of issues still.  I'd like to land the patches
>> that I sent out over the weekend that address memory corruption issues
>> if the server is started without any screens attached.  That issue was
>> made obvious due to the input thread changes which altered our
>> initialization order to reveal the issue.
>> We should also address the use-after-free in CloseDownClient that I
>> discussed in and
>> figure out what's causing replies to get stuck unsent in the first
>> place (cf 9/11: Re: XLoadQueryFont() not returning with recent xserver
>> master).
> 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? 

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.

> -- 
> -keith
_______________________________________________ X.Org development

Reply via email to