Hi all, Now that we are in Feature Freeze, attention turns to bug fixing. As we've done before, we'll establish a point goal - 200pts. Each fixed bug between today and release will count towards that score. Low priority bugs score 3pts, medium 6pts, and high 9pts. When we've hit that list, *AND* closed all the Must-Fix bugs for 0.44.0, we will move into the Hard Freeze phase, and give control over to the release wardens to finalize the release. Needs Fixed in 0.44.x Stable Series ----------------------------------- cyreve 1494337 Fonts/Win: this TTF font crashes Inkscape (pango error) rwst 1467137 Shrinking a pattern causes lock-up cth03 1488128 Snap: Aligning (Snapping) to Grid or Guides does not work joncruz 1418122 Conf corruption when opening files with non-UTF encoded joncruz 1370772 WinXP: Preferences.XML can't be accessed mjwyb 1448811 Connector: assertion failure when moving empty group ishmal 1395505 0.43 crash at startup on Win98se mental 1441003 Misc: flowRoot error with inkscape's svg cyreve 1448618 Fonts: weight variants selection rwst 1493580 SuSE: CVS builds but will not run on Suse 10.0 cth03 1429049 Snap: near-freeze in ObjectSnapper::_findCandidates with ~1000 obj Needs Fixed for 0.45 -------------------- dwyip 1464771 whiteboard: cannot connect to jabber server then crashses cth03 1431560 Snap: Crash at resizing/snapping to guidelines Needs Owner in Order to be Prioritized -------------------------------------- ---- 1484076 potrace freeze with multiple color scan ---- 1475189 Extension ignored by inkscape ---- 1468393 square/circle/polygon/spiral and linked offset misbehaviours ---- 1491646 WIN - Win32 extensions does not call delivered Python ---- 1491925 gradients referenced from masked object disappear ---- 1490430 [INFO NEEDED] Crash in libcairo.dll ---- 1489794 crash with composite ---- 1459502 Crash on imported image update (during Gimp save) ---- 1349761 Inkboard: inkscape crashes when trying to connect Note that I've deliberately kept the list of must-fix bugs for 0.44.0 very lean, so that we can release sooner rather than later. If you disagree and have a bug that you think really must go there, then please speak up now, and explain why it should be a release blocker. Some of the rationale I used for de-ranking bugs: Difficulty confirming the bug. Bug appears to affect just the reporter. Bug doesn't cause crash or data loss. Crash is due to something very unusual (like a specific font, or a directory with unicode characters, or selecting >1000 nodes while snapping is on, etc.) Bug is in a feature not enabled by default (i.e. inkboard). Also note that this list doesn't accept bugs unless they have an owner. This is strictly for pragmatic reasons - without someone volunteering to take care of it, we may end up waiting a very long time to close it. In past releases, we've often ended up simply having to release with these sorts of bugs anyway, so I figure, why accept them as Must Fixes in the first place? ;-) Bryce ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&... _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel