---------- Forwarded message ---------- Date: Fri, 25 Jul 2003 12:38:08 -0400 (CLT) From: Jorge Arellano Cid <jcid@softhome.net> To: Sebastian Geerken <s.geerken@ping.de> Subject: Re: Same bug again... (this forwarded message doesn't include the original attachments) ---------------------------------------- Sebastian,
On Thu, Jul 24, Jorge Arellano Cid wrote:
Sorry for knocking again on the same bug, but please acknowledge you've read my report on the mailing list.
Yes, I received it (and also your other mail today). I'm quite under stress at work due an x mio EUR (or whatever) project presentation :-(
I cannot say when I'll have this bug fixed, I won't have much time at the weekend, but hopefully in the next week.
I understand. BTW, I gave a hand at trying to hunt the bug, and reduced the HTML page to reproduce it (attached), but it also requires a customized slow.c (also attached; it sends by bytes instead of chunks and allows changing the speed). A simple: ...slow?/tmp/b2.html will do. The bug has to do with the new way of handling NOWRAP. Adding more lines to the example table doesn't help, a window resize also doesn't help, but a back/forward fixes it. Hope this findings help.
I really don't want to upload the 0.8.0-pre tarball before 0.7.3 is out, and although a "first impression" is not accurate (agreed!), it helps to calm me down! :-)
I don't know the state of 0.8.0-pre (I had no time to look at it at all), but it may be an option to skip 0.7.3, depending on how much time you estimate until 0.8.0 is mature for release. In this case, I had some time to test and review the new (actually old, but never used) code for incremental resizing.
0.8.0 may take a while before the final release; it is stable but we don't know what issues may spring. It also needs polishing before end users can play with it. One way to solve this problem is to tag current CVS as 0.7.3-rc1, and then upload the truckload of changes that 0.8.0-pre has. Then you can freely work on fixing the bug on 0.7.3-rc1, and when that's done we release 0.7.3 to the public. That way, I can finally let our developers play with 0.8.0-pre from CVS. You get out of the release pressure, and the only thing to be done after 0.7.3 is ready, is to forward port the fixes to CVS (currently 0.8.0-pre is up to date with 0.7.3 CVS). The other goodie that comes from making a 0.7.3 release is that as a long time has passed since our last release, not making this intermediate one would put a lot of pressure on 0.8.0's timeline. Sounds good for you? Best Jorge.-