On Sun, Dec 30, 2007 at 06:01:21PM -0800, Tom Davidson wrote:
Perhaps this would make sense as a bug triage project? A search for broken features that, if they don't get fixed by the end of bug hunt, can be fairly easily disabled and converted to 'wishlist'.
That's a great idea.
What would be the best way to flag/keep track of such things?
I would say, as a minimum, they should be 1. marked Critical, 2. milestoned, and 3. brought up for discussion on the mailing list. These are things that need maximum attention. It's possible if we highlight them strongly enough, some hero can step forward to do the firefighting to get them sorted out.
I don't expect that we'd have so many of these bugs that it will be challenging to keep track of them, but if so, we could introduce a tag for them.
For actually disabling the feature, there's a few ways we can handle it. The best way is to put in an option in Inkscape Preferences for enabling the feature (with an appropriate cautionary statement, maybe marking it experimental or whatever), but ship it turned off by default.
For smaller or more discrete features, it may be simpler to just drop the patch until it's had more development time. But I suspect most of the features we'll be looking at won't fall into this category.
Bryce
On Dec 30, 2007 5:10 PM, Bryce Harrington <bryce@...961...> wrote:
On Sun, Dec 30, 2007 at 04:48:44PM -0800, Tom Davidson wrote:
Is there a point in the development timeline when non-working features should be disabled in order to (temporarily) resolve non-critical bugs?
I'm thinking of the Save with media to zip archive feature ( https://bugs.launchpad.net/inkscape/+bug/168533 ), but perhaps there are others. My feeling is that removing such things is a good way to improve
the
'fit-and-finish' of the release...
Agreed.
Now is a good time to start discussion about cutting broken features. Technically we have until the end of the bug hunt phase for fixes to come in, but if the given feature doesn't seem to be getting worked on, it may be better to disable now, as this gives us extra time for testing to verify nothing breaks in the process, and for getting release notes and docs updated.
Bryce
Tom
On Dec 30, 2007 4:25 PM, Bryce Harrington <bryce@...961...>
wrote:
3 more criticals down! 11 to go. See the prioritized bugs here: https://bugs.launchpad.net/inkscape/+bugs
(The clock icons mean they're ones we've milestoned as must-fixes for 0.46; please lend a hand with getting them figured out!)
Pts BugID Assignee Description
3 171593 Diederik Snapping menu items and shortcuts 3 168912 Johan Engelen axonometric grid angle changes with... 12 168588 Johan Engelen assertion failed, file sp-conn-end.cpp 3 171783 Bulia Byak rclk on palette should change outline color 3 171710 JonCruz Sum color dragging color inother 3 171292 --- Transparency reduced pdf export 9 168865 Johan Engelen Crashes applying "Path along path" effect... 3 171803 Johan Engelen Angled Guidelines! 12 168570 Johan Engelen Crash when recreating grid using 'redo' 9 178004 Max Albert assert when saving as plain svg 3 170374 --- perspective/warp transformation envelope 6 168574 --- Grid setup truncate significant figures 12 178803 theAdib Save As... -> filetype "PDF via Cairo"
crashes
9 178312 Diederik Global 'Enable snapping' option
non-functional
9 177891 Johan Engelen feGaussianBlur crashes when setting fill
paint
9 174475 Niko Kiirala feImage renderer crashes on non-external
image
12 167416 Diederik Shrinking a pattern causes lock-up 9 172778 Johan Engelen Grid settings not respected when reopening
doc
6 167640 Bryce Escaped HTML chars - tooltips show
incorrectly
12 168751 --- crash rm text from path w/ text cursor
active
12 176018 Kees Cook Cairo render prints nothing; bitmap crashes 12 168097 Mental Crash when using clone as clippath 9 179332 Bryce Teeth number in Gears LPE needs tweaking
180 Goal: 500
http://people.ubuntu.com/~brian/project-graphs/inkscape/plots/inkscape-month...http://people.ubuntu.com/%7Ebrian/project-graphs/inkscape/plots/inkscape-month-open.png < http://people.ubuntu.com/%7Ebrian/project-graphs/inkscape/plots/inkscape-mon...
Note: Points are not given for bugs fixed as invalid, dupe, or worksforme, and only for issues that require code changes to fix (not website, translation, or documentation changes).
Note: Scoring for bugs is based on their Importance: Crit=12,
High=9,
Med=6, Low=3, Undecided=3, Wishlist=3.
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel