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] ** (DONE) Review #if 0 code in display/ [mental] ** (DONE) Review #if 0 code in helper/ [mental] ** (DONE) Review #if 0 code in xml/ [mental]
I've mailed out a detailed post about releasing packages, and updated the CreatingDists Wiki page.
We are down to 7 critical bugs that will need to be addressed prior to our final release:
891852 saves to old location after save-as [ted] 850971 (DONE) Crash while deleting namedview in XML editor [bryce] 852976 win32: mouse becoming unresponsive 864791 XML editor: crash when canceling quit [mental] 863373 ./configure not present in nightly tarball snapshot 863371 (DONE) --gnome-print option [jceuppen] 881397 too big objects crash 887428 R&B channels reversed on win32 when printing [ishmal] 871582 path display freeze [mental]
I think we'd all love to see 100% of these fixed, but I figure if we can at least get 2/3rds of them addressed, then we should go ahead with a release. So if we can close 4 more, we should be there.
887428 is fixed but needs to be verified on Windows.
71582 is probably going to be more work than we can do for this release so we may want to leave it 'til next release. Mental, is there a quick hack that could be done to at least prevent Inkscape from freezing up when zooming out? Could you write up your thoughts on how the code should be rewritten for a proper fix?
Bulia, you mentioned you were going to look at 891852 - did you get a chance to trace down what needs to be done?
Rejon, any luck with figuring out the configure issue?
Bob, have you been able to get into SourceForge to take a look at the bugs? I can forward you the text of them if not. I think there's 2-3 that hopefully will be quick for you to validate and close for us.
Mental, I bet that there's probably a quick fix for 864791. If you won't have time for it today, I might have a chance to look at it tonight or tomorrow night.
Finally, would someone mind banging on Inkscape a bunch today looking for crashes, or if there are any features that aren't working?
Bryce