[Xcb] Next Release?

[Uli Schlachter]

Morning,

On 04.10.2013 12:47, Arnaud Fontaine wrote:
> Hi,
> 
> I'm also interested in having libxcb released (mainly for xkb), so here
> are some updates about the status of the release.
> 
> Uli Schlachter <psychon at znc.in> writes:
> 
>> On 06.08.2013 19:55, Uli Schlachter wrote:
> 
>>> Also, we have "fix deadlock with xcb_take_socket/return_socket v3" in git
>>> and I think I remember that someone wanted some more testing & making sure
>>> that this commit is good before doing a release.
>>
>> Jamey asked for holding back releases until we have some clear picture on
>> this. I don't want to try to summarize the discussion, so the relevant mail
>> (and the thread that it belongs to) can be found here:
>> http://lists.freedesktop.org/archives/xcb/2013-June/008340.html
>>
>> There is also the following patch from Christian and the replies to it.
>> However, I don't mind ignoring it for now (but would be happy if we could
>> reach some consensus about it):
>> http://lists.freedesktop.org/archives/xcb/2013-May/008272.html
> 
> If no consensus can be reached on this issue, then it could be probably
> reverted until then, otherwise we never release. What do you think?

Yeah, I agree. Although I can already see that this means "Don't call into xcb
while holding the Xlib lock" and the patch never gets merged.

So feel free to revert 9ae84ad187e (unless someone else says otherwise?).

[...]
> Peter Harris <pharris at opentext.com> writes:
> 
>> My short-term plan, if I ever get a free minute, is to convert the
>> events into structs (deleting the type field) and add one event that
>> contains the type and a union with all the structs.
> 
> Done by Daniel Martin but not merged yet:
> http://lists.freedesktop.org/archives/xcb/2013-August/008541.html
> 
> Should it be merged?
> 
> 
> Also, here is a list of patches sent after Uli initial email and which
> have not been merged yet (they would be probably worth including in the
> release):
> 
[...]
> * [Bug 68387] New: xinput2 XIQueryDevice reply not read correctly
>   https://bugs.freedesktop.org/show_bug.cgi?id=68387

XInput is still disabled by default, so I don't think that this is a blocker.

> * [Bug 69118] New: Unix spool is located at /var/spool/sockets/X11/... or /usr/spool/sockets/X11/... under HPUX
>   https://bugs.freedesktop.org/show_bug.cgi?id=69118

No real opinion here. If no one wants the patch in, I guess that this will end
up being another patch in the bug tracker which bitrots away.

...which isn't really good. So even if this shouldn't block the release, it
would be nice if this can get a final ACK or NAK.

[...]
> Unless somebody steps up, I will merge the patches with a Reviewed-By.
> What should we do about the others?
> 
> 
> Anything else missing?

>From the top of my head: Nope.

Cheers,
Uli
-- 
Bruce Schneier can read and understand Perl programs.