Minutes from August 6 Release Wranglers call
Kevin E Martin
kem at freedesktop.org
Sun Aug 8 19:18:12 PDT 2004
On Sat, Aug 07, 2004 at 04:47:58AM +0200, Roland Mainz wrote:
> There are a couple of build bustage issues which should be considered,
> too:
> - https://freedesktop.org/bugzilla/show_bug.cgi?id=997 ("Build failure
> with |#define BuildXfixes NO|")
I've looked into this one and there were two problems here. The changes
have been checked in. See the bugzilla report for the details.
> - https://freedesktop.org/bugzilla/show_bug.cgi?id=570 ("Build with
> |#define BuildDPMS NO| fails")
I've looked into these problems and fixed them.
> - https://freedesktop.org/bugzilla/show_bug.cgi?id=993 ("Build failure
> with |#define BuildXevie NO|")
I've checked in changes to fix this problem (and another one that the
first fix uncovered). The changes I had to make to event.c seemed
reasonable, but I would appreciate it if someone more familiar with
Xevie could look at the solution to make sure everything still works
properly.
Also, this brings up an issue that was raised on the xorg at fdo mailing
list: Are we going to keep Xevie in Xext or are we going to put it into
a library of its own?
> - https://freedesktop.org/bugzilla/show_bug.cgi?id=906 ("CVS trunk does
> not compile with |#define OptimizedCDebugFlags -g -DDEBUG|")
Could someone start looking into this one? There are numerous failures
with -DDEBUG. This is going to take a while to sort out.
> Another issue which cases headaches for me is
> https://freedesktop.org/bugzilla/show_bug.cgi?id=961 ("Xnest crashes in
> damagePaintWindow()"): Xnest doesn't seem to start anymore... ;-(
I have not been able to reproduce this one on an IA-32 box. There have
been quite a few changes since the bug report was filed, so I don't know
if this still occurs. Please verify that it still happens on your AMD64
box.
> Finally:
> Is it allowed to update manual pages and other documentation during the
> freeze (https://freedesktop.org/bugzilla/show_bug.cgi?id=811 comes in
> mind) ?
Yes, documentation fixes are both still allowed and encouraged.
More information about the release-wranglers
mailing list