We've met the bug fixing goal! (More below.)

Bug ID Pts Title ------------------------------------------------------------------------ 955020 6 assert when quitting with dialog and duplicated window 993447 3 Wrong export area 1022832 3 File dialog glibmm Warning 994853 3 dialog title handled with wrong encoding 1029755 3 png resolution not imported 1039109 9 various problems with text after refactoring 980065 6 Garbled display in "pattern" fill dialog 1048802 6 2 find dialogs 1029530 (dup) WIN CVS: crash on file | import 1051350 (dup) Crash when open a file 990659 6 ill2svg fails without Image/Magick 1054270 9 Win32: Aligning objects causes crash 1048614 6 export: "selection" not toggled with text 931496 6 image URL not updating 998672 (dup) printing broken on Windows XP 1001279 6 Version: 0.39-suse91.0 rpm needs libpopt.so.0 1012089 6 CVS snapshots no longer available 996493 (dup) .39 Inkscape freezes 992962 3 Build Warning: Extensions warnings 992986 3 Build Warning: deprecated functions 992987 3 Build Warning: missing constructors 992985 3 Build Warning: unused variables/functions 1004134 6 'Changed' flag cleared when save not successful 1041643 3 Files fail to open on Gnome 2.8 1048151 6 Union destroy objects in some cases 984096 9 Assertion failures with calligraphy tool 1045067 3 --without-gui crashes if home dir not writable 1038932 6 Export silently fails when file cannot be created 984854 9 crashes with non-existent gradient in gradient editor 1000350 9 --print option can attempt to open dialogs and segfault 1041757 (dup) undefined symbol: gdk_threads_lock 993294 9 RDF improperly exported with plain SVG 1024915 9 glib-2.5.2: crashes on clicking fill and stroke dialog ======================================================================== Total: 159 Goal: 150pts (106% towards goal)

It's amazing how swiftly the bug fixing has been going - I'd estimated it'd take us 2-3 weeks to close this many bugs, yet we're done after just over half a week. If you're still intent on bug fixing, keep at it! There's still plenty of bugs listed, and I'll keep the counter running to rack up extra credit. :-)

What remains to be done before we enter into a code freeze is the implementation of layer editing UI. As mental mentioned earlier, this is a key feature that we need to ensure is usable for users. So if you have time to do some Gtk+ implementation work this weekend, look at helping with one of the tasks he's listed in the roadmap: http://www.inkscape.org/cgi-bin/wiki.pl?Roadmap

Meantime, as Bulia suggests, while this work is going on this is a good time to really put the codebase to some heavy duty use and see if there's any new bugs or performance problems we haven't heard of yet.

At this point, it would be wise to taper off on new code, other than the layer UI work, and focus on bugs/testing, layer UI, packaging, and docs. Depending on how much gets done towards the layer UI this weekend, I estimate we are probably within 0.5 to 1.5 weeks away from a hard freeze.

Bryce