Hey All,
It appears that the Frost is nearing completion, and the Feature Freeze will be setting in soon. Given this, it's probably a good time to start putting together a list of release blocker bugs, as well as discuss if any features need to be pruned due to them being incomplete.
For reference, here are the bugs that are still milestoned for 0.47: https://edge.launchpad.net/inkscape/+milestone/0.47
Is anyone aware if there currently any major platform specific bugs like we had around 0.46? (win32 printing issue is what I speak of)
Also, JonCruz, should we hold back the "Auto" swatch palette from this release?
At this point I want to again remind people to ensure that the release notes are as up-to-date as possible! Please take a moment to ensure that your improvements/enhancements/new features are all mentioned with a brief explanation where necessary.
Thanks to everyone for your contributions!
Cheers, Josh
On Aug 12, 2009, at 4:16 PM, Joshua A. Andler wrote:
Also, JonCruz, should we hold back the "Auto" swatch palette from this release?
The next few days should show this. Among other slowdowns, X11 stopped working for my on OS X 10.4.x. I'll probably be able to go into linux and work on this, but it did block even remote X from a workflow.
Of course, if things don't settle out quickly then it is very easy to do an #ifdef so that individuals can turn it on to experiment with, yet leave it out for the actual release builds.
Hi,
De : Joshua A. Andler <scislac@...400...> It appears that the Frost is nearing completion, and the Feature Freeze will be setting in soon. Given this, it's probably a good time to start putting together a list of release blocker bugs, as well as discuss if any features need to be pruned due to them being incomplete.
Two very annoying bugs:
#304018 Crash when using LPE with node tool selected (https://bugs.edge.launchpad.net/inkscape/+bug/304018) #307195 crash with two inkscape instances when changing layer (https://bugs.edge.launchpad.net/inkscape/+bug/307195) They lead to a crash, are regressions, and appear in very common situations. Thus I think they are release blockers.
And three incomplete (or not working) features:
#346721 Segfault after opening scripts dialog (https://bugs.edge.launchpad.net/inkscape/+bug/346721) Not very annoying (I'm not sure lots of users use it) but since it's an UI menu entry, it should work or be removed (also a regression). It should not be too hard to fix (see bug report).
#179452 export to openclipart.org in dev version (https://bugs.edge.launchpad.net/inkscape/+bug/179452) I've recently postponed and lowered the report. It should be disabled in 0.47.
#319107 Jabber whiteboard doesn't work (https://bugs.launchpad.net/inkscape/+bug/319107). Should also be disabled in 0.47.
Is anyone aware if there currently any major platform specific bugs like we had around 0.46? (win32 printing issue is what I speak of)
#166678 Paper size or orientation are not used when printing (https://bugs.edge.launchpad.net/inkscape/+bug/166678) and #220360 win32 fails to print in large format (A0) (https://bugs.edge.launchpad.net/inkscape/+bug/220360) are now fixed!
At this point I want to again remind people to ensure that the release notes are as up-to-date as possible!
And create a new Keys and Mouse reference for 0.47 (22062 is linked to http://inkscape.org/doc/keys046.html).
Cheers, -- Nicolas
2009/8/13 Nicolas Dufour <nicoduf@...48...>:
Two very annoying bugs:
#307195 crash with two inkscape instances when changing layer (https://bugs.edge.launchpad.net/inkscape/+bug/307195)
I actually tried to look into this a while ago. I seem to remember that the (way towards a) solution revealed some more fundamental issues, but I can't remember exactly what it was. I'll try to dig it up, but if I'm unlucky it may take a few days before I get around to doing it.
Max
On Thu, Aug 13, 2009 at 5:11 AM, Nicolas Dufour<nicoduf@...48...> wrote:
#304018 Crash when using LPE with node tool selected (https://bugs.edge.launchpad.net/inkscape/+bug/304018)
fixed in 22074, please test
On 13/8/09 10:11, Nicolas Dufour wrote:
#166678 Paper size or orientation are not used when printing (https://bugs.edge.launchpad.net/inkscape/+bug/166678) [...] are now fixed!
It doesn't work for me when opening and printing a document which was saved with landscape orientation. Only after toggling the document property to 'Portrait' and back to 'Landscape' the print dialog picks up the correct paper/page orientation. Can anyone confirm this on other platforms than OS X?
~suv
On Wed, 2009-08-12 at 16:16 -0700, Joshua A. Andler wrote:
Hey All,
It appears that the Frost is nearing completion, and the Feature Freeze will be setting in soon. Given this, it's probably a good time to start putting together a list of release blocker bugs, as well as discuss if any features need to be pruned due to them being incomplete.
#407893: Text Tool attributes messed up.
#382313: Image Filter broken for external images. This is a serious regression in my opinion.
#397075: Inkscape crashes adding image effect in filter editor.
Important... but maybe not a blocker:
#389130 Inkscape PNG transparency display appearance does not match export and other standard applications
Tav
On Thu, Aug 13, 2009 at 6:08 AM, Tavmjong Bah<tavmjong@...8...> wrote:
#407893: Text Tool attributes messed up.
fixed in 22080, please test
All the Windows-specific issues that I'm aware of have been fixed now, and I've done all the work I'm doing for a while fixing up the Windows installer (still got uninstallation routine optimisation and more complex language stuff to add in, but that'll need quite a bit of string translation as well). Also all the Inkscape Portable-related issues have been ironed out (thanks particularly to Jon Cruz for committing my first patch for an alternative setting storage location and theAdib for working out the export dialogue file chooser window :-) ) I'm looking forward to the release of 0.47 (especially so that Inkscape Portable will be released at PortableApps.com :D )!
On Thu, Aug 13, 2009 at 9:16 AM, Joshua A. Andler <scislac@...400...> wrote:
Hey All,
It appears that the Frost is nearing completion, and the Feature Freeze will be setting in soon. Given this, it's probably a good time to start putting together a list of release blocker bugs, as well as discuss if any features need to be pruned due to them being incomplete.
For reference, here are the bugs that are still milestoned for 0.47: https://edge.launchpad.net/inkscape/+milestone/0.47
Is anyone aware if there currently any major platform specific bugs like we had around 0.46? (win32 printing issue is what I speak of)
Also, JonCruz, should we hold back the "Auto" swatch palette from this release?
At this point I want to again remind people to ensure that the release notes are as up-to-date as possible! Please take a moment to ensure that your improvements/enhancements/new features are all mentioned with a brief explanation where necessary.
Thanks to everyone for your contributions!
Cheers, Josh
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Thanks,
Chris Morgan <chris.morganiser@...400...>
I don't need a quote in my signature. It's hard enough surviving as it is without having to find a meaningful quote. Will you forgive me? Or don't you read this bit?
On 13/8/09 01:16, Joshua A. Andler wrote:
It appears that the Frost is nearing completion, and the Feature Freeze will be setting in soon. Given this, it's probably a good time to start putting together a list of release blocker bugs, as well as discuss if any features need to be pruned due to them being incomplete.
PDF export: text to path still broken
Bug #388257 “Inkscape 0.47Pre: PDF/PS Export 'Text to Paths' gives inconsistent results” https://bugs.launchpad.net/inkscape/+bug/388257
numeric precision crash:
Bug #399604 “'malloc: *** error' after changing numeric precision to 1 or 2” https://bugs.launchpad.net/inkscape/+bug/399604
technical drawing: geometric bbox mode barely useful for precise values
Bug #190557 “resize of object or group by entering a numeric size results in a different size.” https://bugs.launchpad.net/inkscape/+bug/190557
Is anyone aware if there currently any major platform specific bugs like we had around 0.46? (win32 printing issue is what I speak of)
not working features on OS X:
Bug #390024 “raster image extensions fail on osx: missing ImageMagick config files/resources” https://bugs.launchpad.net/inkscape/+bug/390024
Bug #373514 “No Script Console on Mac OS X” https://bugs.launchpad.net/inkscape/+bug/373514
~suv
I would vote for:
376068 Inkscape 0.46_5 Segmentation fault on gradient edit an gui element is accessed in the dialoge after the removal from screen currently the crash comes from assert function thus is can be converted to "close this dialogue" or something else
376068 Inkscape 0.46_5 Segmentation fault on gradient edit this is an transition problem from inkscape floating point precistion to cairo-based integer calculation the calculated value is a NaN. In this case the crash can be prevented by ignoring the element or so.
Adib.
On Thu, Aug 13, 2009 at 1:16 AM, Joshua A. Andler<scislac@...400...> wrote:
Hey All,
It appears that the Frost is nearing completion, and the Feature Freeze will be setting in soon. Given this, it's probably a good time to start putting together a list of release blocker bugs, as well as discuss if any features need to be pruned due to them being incomplete.
For reference, here are the bugs that are still milestoned for 0.47: https://edge.launchpad.net/inkscape/+milestone/0.47
Is anyone aware if there currently any major platform specific bugs like we had around 0.46? (win32 printing issue is what I speak of)
Also, JonCruz, should we hold back the "Auto" swatch palette from this release?
At this point I want to again remind people to ensure that the release notes are as up-to-date as possible! Please take a moment to ensure that your improvements/enhancements/new features are all mentioned with a brief explanation where necessary.
Thanks to everyone for your contributions!
Cheers, Josh
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Thu, Aug 13, 2009 at 4:49 PM, the Adib<theadib@...1439...> wrote:
I would vote for:
376068 Inkscape 0.46_5 Segmentation fault on gradient edit
fixed in 22079
376068 Inkscape 0.46_5 Segmentation fault on gradient edit this is an transition problem from inkscape floating point precistion to cairo-based integer calculation the calculated value is a NaN. In this case the crash can be prevented by ignoring the element or so.
you gave the same bug number?
On Fri, Aug 14, 2009 at 12:16 AM, bulia byak<buliabyak@...400...> wrote:
On Thu, Aug 13, 2009 at 4:49 PM, the Adib<theadib@...1439...> wrote:
I would vote for:
376068 Inkscape 0.46_5 Segmentation fault on gradient edit
fixed in 22079
that was fast :-)
376068 Inkscape 0.46_5 Segmentation fault on gradient edit this is an transition problem from inkscape floating point precistion to cairo-based integer calculation the calculated value is a NaN. In this case the crash can be prevented by ignoring the element or so.
you gave the same bug number?
should be: 406470 Crash when trying to save as PDF
HTH, Adib.
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
participants (9)
-
bulia byak
-
Chris Morgan
-
Jon A. Cruz
-
Joshua A. Andler
-
Maximilian Albert
-
Nicolas Dufour
-
Tavmjong Bah
-
the Adib
-
~suv