Wow, 45 points worth of bugs closed today has put us well over the top of our goals. Nice! :-)
Bug ID# PRI Owner Description ------------------------------------------------------------------------ 1095300 6 ishmal WIN: Save as: no formats to choose from 1082188 9 joncruz Linux: File->Import crash 1044322 6 joncruz Relative Locations <image> tags. 1085586 6 bulia Error in opening AI / EPS file 1103936 6 bulia Bad markup found in translations 1109223 6 mental CVS: Error using calligraphy tool 1108231 6 mental sp_repr_set_position_absolute breakage 1108620 9 joncruz Drag and drop case sensitive 1107775 3 pjrm wrong paper sizes 1105787 9 johncl Installation problem: libatk-1.0-0.dll not found 990677 6 ted readme needed for extensions 1107562 9 bulia Node Align Crash 1101210 3 bulia CVS: Flowtext not working 1103001 3 ted Grid is shown non-uniform 1102318 9 kees Crash on "save as" 1104741 6 bulia Printout 25% too large 1105352 6 pjrm Markers are not shown in Plain-SVG-Export 1075860 9 pjrm WIN: assert when doing stamping during move 1080252 9 bryce crash on intersectiion 1068116 6 mental complie error in gc.cpp with inkscape-20041116 1076872 6 kees ngettext isn't used 933461 6 kees Win32 Install Directories 1068299 6 kees Build failure on mips(el) 1100675 6 mental svg tag requires xmlns attribute in CVS2005-01-10 1097652 9 pjrm crash on whitespace property value ------------------------------------------------------------------------ Current: 165 Goal: 150
Feature Freeze - Jan 26 Hard Freeze - Feb 1 Release - Feb 5-6
Bryce
On Sat, 8 Jan 2005, Bryce Harrington wrote:
Okay, since there were no comments to the contrary, I suppose it's safe to assume this proposal is acceptable to everyone. If not, lemme know. We'll shoot for 150 points for low/med/high (3/6/9 pts) that are closed as FIXED (i.e., no points for dups, won't fix, invalid, etc.) and that are confirmed as present in 0.40 or in CVS.
Bryce
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Thu, 2005-01-27 at 20:33, Bryce Harrington wrote:
Wow, 45 points worth of bugs closed today has put us well over the top of our goals. Nice! :-)
Unfortunately we have a severe crash bug on Amd64 and PPC platforms at least (#1107922). That MUST get fixed before we can even think about releasing.
-mental
On Fri, 28 Jan 2005, MenTaLguY wrote:
On Thu, 2005-01-27 at 20:33, Bryce Harrington wrote:
Wow, 45 points worth of bugs closed today has put us well over the top of our goals. Nice! :-)
Unfortunately we have a severe crash bug on Amd64 and PPC platforms at least (#1107922). That MUST get fixed before we can even think about releasing.
Why? We've never claimed AMD64 or PPC support before, afaik. Do we even have active developers on those systems? As far as I know the developers are mainly all 32-bit x86 based...
Please give a more detailed case for why this should be accepted as a release-stopper bug. This has been in the tracker for a while but this is the first time it has been identified as a potential showstopper.
Note that ideally, showstopper bugs should be identified at the start of the bugfixing phase, not the end of it. ;-)
Bryce
On Fri, 28 Jan 2005 17:44:29 -0800 (PST), Bryce Harrington <bryce@...260...> wrote:
Please give a more detailed case for why this should be accepted as a release-stopper bug. This has been in the tracker for a while but this is the first time it has been identified as a potential showstopper.
1) It's recent. 2) I listed it as critical in my "critical bugs" message. 3) It was reported by two people already one of which is Jimmac (he's on a Powerbook). 4) If it crashes on PPC this means something is very broken in the code, even if it happens not to crash on i86.
It absolutely must be fixed.
On Fri, 28 Jan 2005, bulia byak wrote:
On Fri, 28 Jan 2005 17:44:29 -0800 (PST), Bryce Harrington <bryce@...260...> wrote:
Please give a more detailed case for why this should be accepted as a release-stopper bug. This has been in the tracker for a while but this is the first time it has been identified as a potential showstopper.
- It's recent. 2) I listed it as critical in my "critical bugs"
message. 3) It was reported by two people already one of which is Jimmac (he's on a Powerbook). 4) If it crashes on PPC this means something is very broken in the code, even if it happens not to crash on i86.
It absolutely must be fixed.
Okay, thanks, that is a good case for this being a must fix.
I think before we accept it, though, we also need a commitment from someone to own the bug. I am worried if we have unowned must-fix bugs, then the release schedule will get messed up.
I'll go over your critical bug list and identify ones that look acceptable as showstoppers and which need more.
Next release, I think we need to be more stringent about getting the must-fix list identified earlier on in the release cycle, so that there is more time to work on them. The only reason I felt comfortable setting dates was because I had asked for must fix bugs, and none were identified (in fact, iirc you had said you were comfortable going ahead with the release)...
Bryce
On Fri, 28 Jan 2005 18:17:20 -0800 (PST), Bryce Harrington <bryce@...260...> wrote:
Next release, I think we need to be more stringent about getting the must-fix list identified earlier on in the release cycle, so that there is more time to work on them. The only reason I felt comfortable setting dates was because I had asked for must fix bugs, and none were identified (in fact, iirc you had said you were comfortable going ahead with the release)...
I said I was OK with feature freeze, i.e. I agreed to stop working on features and start looking into bugs.
On Fri, 28 Jan 2005, bulia byak wrote:
On Fri, 28 Jan 2005 18:17:20 -0800 (PST), Bryce Harrington <bryce@...260...> wrote:
Next release, I think we need to be more stringent about getting the must-fix list identified earlier on in the release cycle, so that there is more time to work on them. The only reason I felt comfortable setting dates was because I had asked for must fix bugs, and none were identified (in fact, iirc you had said you were comfortable going ahead with the release)...
I said I was OK with feature freeze, i.e. I agreed to stop working on features and start looking into bugs.
Right, but my point is still valid - I think we must identify the must-fix bugs much earlier on in the process, preferrably before any freeze consideration. It is silly to wait until the last moment to start working on these sorts of bugs. If I'm made aware of these earlier on, I can plan accordingly. As it is, now we either have to triage those down, or postpone the release.
I will have a shot at triaging the list tonight or tomorrow.
Meanwhile, please review whether the layer movement features are critical. Mental has stated he cannot finish it by the 1st, and no one has volunteered to help, so there appears to be a problem here. If you can find a volunteer, it may still be possible, otherwise we must either drop the feature or postpone the release.
Bryce
On Fri, 2005-01-28 at 20:48, bulia byak wrote:
- If it crashes on PPC this means
something is very broken in the code, even if it happens not to crash on i86.
That one point probably deserves underscoring, actually. That it happens on both PPC and AMD64, which are pretty dissimilar platforms, suggests a serious code (rather than a toolchain) problem to me.
-mental
On Fri, 2005-01-28 at 17:44 -0800, Bryce Harrington wrote:
Why? We've never claimed AMD64 or PPC support before, afaik. Do we even have active developers on those systems? As far as I know the developers are mainly all 32-bit x86 based...
I realize that I'm behind on this entire discussion -- but just FYI I develop/use PPC.
--Ted
There was a request to see an updated bug status, so here ya go:
Bug ID# PRI Owner Description ------------------------------------------------------------------------ 1113238 9 bulia crash when using multiple views 1109933 3 scislac Download page clarity 1113316 6 kees losing metadata 934062 6 kees win32: international characters in home path 1104050 6 kees PS printing fails to deselect dashed brush 1025565 9 kees Crash with "1979" font 1107305 9 kees Cannot start 1075640 9 kees Win32: Spiral editing, divergence=0.00 may cause a crash 1111355 9 bryce fails when ctrl-dragging an object and hitting escape key 1055034 9 bryce 0.40CVS Stuck on startup when compiled with GCC 3.4.2 1085394 3 bulia grid snapping must be off when grid is hidden 1073459 9 bulia Win32 : open/import file, typing text freezes inkscape 1111842 6 bulia Width x Height status in mm only 1066052 6 mental hang during ungroup (or print) 1111065 6 bulia Exporting selection merges onto background.
1095300 6 ishmal WIN: Save as: no formats to choose from 1082188 9 joncruz Linux: File->Import crash 1044322 6 joncruz Relative Locations <image> tags. 1085586 6 bulia Error in opening AI / EPS file 1103936 6 bulia Bad markup found in translations 1109223 6 mental CVS: Error using calligraphy tool 1108231 6 mental sp_repr_set_position_absolute breakage 1108620 9 joncruz Drag and drop case sensitive 1107775 3 pjrm wrong paper sizes 1105787 9 johncl Installation problem: libatk-1.0-0.dll not found 990677 6 ted readme needed for extensions 1107562 9 bulia Node Align Crash 1101210 3 bulia CVS: Flowtext not working 1103001 3 ted Grid is shown non-uniform 1102318 9 kees Crash on "save as" 1104741 6 bulia Printout 25% too large 1105352 6 pjrm Markers are not shown in Plain-SVG-Export 1075860 9 pjrm WIN: assert when doing stamping during move 1080252 9 bryce crash on intersectiion 1068116 6 mental complie error in gc.cpp with inkscape-20041116 1076872 6 kees ngettext isn't used 933461 6 kees Win32 Install Directories 1068299 6 kees Build failure on mips(el) 1100675 6 mental svg tag requires xmlns attribute in CVS2005-01-10 1097652 9 pjrm crash on whitespace property value ------------------------------------------------------------------------ Current: 270 Goal: 150
Feature Freeze - Jan 26 Hard Freeze - Feb 1 Release - Feb 5-6
participants (4)
-
Bryce Harrington -
bulia byak -
MenTaLguY -
Ted Gould