I think the time's right to go ahead and feature freeze and put full focus on bug fixing. Let's set the feature freeze time to Saturday 20:00 GMT (that's high noon for those of us in the PST timezone).
Here are the remaining code cleanup tasks:
** Review #if 0 code in sp-gradient.cpp, sp-root.cpp [tvon] ** Review #if 0 code in *-chemistry.cpp and seltrans.cpp [pjrm] ** Review #if 0 code in svg/ ** Review #if 0 code in display/ [mental] ** Review #if 0 code in helper/ ** Review #if 0 code in xml/
I haven't seen tvon in a while so perhaps someone else can take his review task?
I will post the info on making release packages tomorrow morning.
We are down to 9 critical bugs that will need to be addressed prior to our final release:
891852 saves to old location after save-as 850971 Crash while deleting namedview in XML editor 852976 win32: mouse becoming unresponsive 871582 path display freeze [mental] 864791 XML editor: crash when canceling quit [mental] 863373 ./configure not present in nightly tarball snapshot 863371 --gnome-print option 881397 too big objects crash 887428 R&B channels reversed on win32 when printing [ishmal]
The ./configure issue looks like just a tweak needed to the nightly build script - Ted or Jon, perhaps you could solve this easily?
Ishmal, could you verify that the mouse unresponsive bug on Win32? It's possible this bug is completely fixed now. Also see if you can validate the fix that mental did for 881397, that it works on Win32 too; if so we can mark that one done too.
The --gnome-print option bug looks like it might be spurious and not need fixing - could someone try doing `./configure --with-gnome-print` and see if they can reproduce the bug? Jon?
There are a couple XML Editor bugs; I looked into each and they did not look as trivial as some of the other bugs. Could someone figure out what we could do to fix these?
Mental, do you think 871582 is fixable this weekend? If not, how critical is the bug - could it be postponed for next release?
Bryce
Here are the remaining code cleanup tasks:
** Review #if 0 code in sp-gradient.cpp, sp-root.cpp [tvon] ** Review #if 0 code in *-chemistry.cpp and seltrans.cpp [pjrm] ** (DONE) Review #if 0 code in svg/ [bryce] ** Review #if 0 code in display/ [mental] ** (DONE) Review #if 0 code in helper/ [bryce] ** Review #if 0 code in xml/
We are down to 9 critical bugs that will need to be addressed prior to our final release:
891852 saves to old location after save-as 850971 Crash while deleting namedview in XML editor 852976 win32: mouse becoming unresponsive 871582 path display freeze [mental] 864791 XML editor: crash when canceling quit [mental] 863373 ./configure not present in nightly tarball snapshot 863371 --gnome-print option 881397 too big objects crash 887428 R&B channels reversed on win32 when printing [ishmal]
There are also some priority-6 (medium criticality) bugs like 866197 "problems with non-ascii filenames" that would be nice to fix.
Bryce
The ./configure issue looks like just a tweak needed to the nightly build script - Ted or Jon, perhaps you could solve this easily?
Ishmal, could you verify that the mouse unresponsive bug on Win32? It's possible this bug is completely fixed now. Also see if you can validate the fix that mental did for 881397, that it works on Win32 too; if so we can mark that one done too.
The --gnome-print option bug looks like it might be spurious and not need fixing - could someone try doing `./configure --with-gnome-print` and see if they can reproduce the bug? Jon?
There are a couple XML Editor bugs; I looked into each and they did not look as trivial as some of the other bugs. Could someone figure out what we could do to fix these?
Mental, do you think 871582 is fixable this weekend? If not, how critical is the bug - could it be postponed for next release?
Bryce
On 8 Feb 2004, Johan Ceuppens wrote:
On Sat, 7 Feb 2004 12:17:57 -0800 (PST) Bryce Harrington <bryce@...1...> mused:
863371 --gnome-print option
I've committed a fix to CVS but I couldn't test the printing fully.
Thanks, hopefully it'll work well. Can you put a mention of this in the release notes, so if users do run into some issues, they are aware of what's up and can report accordingly?
Bryce
On Sat, 2004-02-07 at 03:38, Bryce Harrington wrote:
Mental, do you think 871582 is fixable this weekend? If not, how critical is the bug - could it be postponed for next release?
It's probably not extremely critical; we're certainly not going to be able to fix it in time for the release, anyway.
It's hitting a corner case and getting stuck in an infinite loop in nr_svl_uncross_full(), just below where Lauris marked it "This is bitch" ... it's a huge function, much of which seems to have evolved through trial and error rather than any sort of formal basis.
Probably the only way to fix it is to rewrite it.
-mental
Bryce wrote:
881397 too big objects crash
Ishmal, could you verify that the mouse unresponsive bug on Win32? It's possible this bug is completely fixed now. Also see if you can validate the fix that mental did for 881397, that it works on Win32 too; if so we can mark that one done too.
Bryce, How big is too big? I cannot get in to SourceForge to see the bug. However, I can open and play with SVG files of >1MB and the system does not crash. It gives me some messages sometimes but chugs along after that. One file comes up with its scale wrong but still no crash. I am win2000build040208.
vellum
participants (4)
-
Bryce Harrington -
Johan Ceuppens -
MenTaLguY -
vellum