5:18 a.m.
(I originally sent this using the wrong email address. I'm expecting that one
to bounce back, which is why I'm sending this one. If you see this message
twice I apologize profusely.)
I'm a little stuck on the proper "etiquette" for reporting a regression.
I've been playing around with the test builds for Inkscape and I've noticed a
regression. In 2009 or thereabouts there was a KDE bug that prevented you from
using guides -- if you tried to drag a guide down from either of the rulers,
you wound up dragging the entire window around instead. That bug was fixed,
but it appears to be back.
What's the best way to report that? Should I locate the original bug report
(which is probably closed at this point) and add a comment noting that it is
back, or should I enter a new bug report and reference that one?
(Of course it could be that someone else has already reported this. I didn't
find the new bug report, though, just the old one.)
Christopher B. Wright (wrightc@...537...)
5:23 a.m.
On Tue, 15 Jan 2013 08:18:39 -0500
"Christopher B. Wright" <wrightc@...537...> wrote:
http://inkscape.org/report_bugs.php
--
Regards,
Frank
"Byte my kernel"
--me .
5:29 a.m.
New subject: Regression in test Inkscape builds. How to file bug?
I know how to report the bug. That's not my question. This is probably
something most of you are already familiar with, but I've never been in a
situation where the bug I'm reporting is one that was already fixed at one
point, and has come back. (i.e., a regression).
Is it more appropriate to add a comment to the existing (closed) bug, or open
a new one and link to the existing (closed) bug?
Nine times out of ten when I've introduced bugs that I thought were new (but
had already been reported), I see an admin either closing it as a duplicate or
linking to the duplicate, but in those cases the original bug is still open.
I'm not sure what the preferred action is when the original bug is CLOSED but
it's come back.
On Tuesday, January 15, 2013 01:23:10 PM you wrote:
On Tue, 15 Jan 2013 08:18:39 -0500
"Christopher B. Wright" <wrightc@...537...> wrote:
http://inkscape.org/report_bugs.php
5:33 a.m.
On Tue, 15 Jan 2013 08:18:39 -0500
"Christopher B. Wright" <wrightc@...537...> wrote:
(I originally sent this using the wrong email address. I'm
expecting that one to bounce back, which is why I'm sending this
one. If you see this message twice I apologize profusely.)
Apologies, reply based on your Subject.
File a new bug against the version that has the problem,
after *first* checking is the same version bug existing.
--
Regards,
Frank
"Byte my kernel"
--me .
5:55 a.m.
New subject: Regression in test Inkscape builds. How to file bug?
On Tuesday, January 15, 2013 01:33:55 PM Frank Murphy wrote:
On Tue, 15 Jan 2013 08:18:39 -0500
"Christopher B. Wright" <wrightc@...537...> wrote:
> (I originally sent this using the wrong email address. I'm
> expecting that one to bounce back, which is why I'm sending this
> one. If you see this message twice I apologize profusely.)
Apologies, reply based on your Subject.
File a new bug against the version that has the problem,
after *first* checking is the same version bug existing.
I did check. The bug exists, was reported about five years ago, and was, at
the time, fixed.
So what I want to know:
Do I add a comment to the original bug report, even though that specific
instance of the bug was fixed?
Or do I create a new bug report, and reference the bug report where it
originally occurred?
What's tripping me up is that the bug was fixed, and the bug report is
therefore "closed." (I note that Inkscape doesn't actually seem to have a
"closed" status, but "fixed" seems to play the same role.)
On the one hand, adding a comment to the end of a fixed bug will prevent
duplication... but if it's "fixed," am I commenting on something no one will
ever look at? On the other hand, creating a new bug report will ensure someone
looks at it, but am I just creating needless work for someone who is going to
have to close the report because it already exists?
Christopher B. Wright (wrightc@...537...)
8:31 a.m.
New subject: Regression in test Inkscape builds. How to file bug?
Christopher,
If there has been an actual official release with the bug fixed,
please just file a new report and you can certainly link to the old
report if you want to.
Cheers,
Josh
On Tue, Jan 15, 2013 at 5:55 AM, Christopher B. Wright
<wrightc@...537...> wrote:
On Tuesday, January 15, 2013 01:33:55 PM Frank Murphy wrote:
> On Tue, 15 Jan 2013 08:18:39 -0500
>
> "Christopher B. Wright" <wrightc@...537...> wrote:
> > (I originally sent this using the wrong email address. I'm
> > expecting that one to bounce back, which is why I'm sending this
> > one. If you see this message twice I apologize profusely.)
>
> Apologies, reply based on your Subject.
>
> File a new bug against the version that has the problem,
> after *first* checking is the same version bug existing.
I did check. The bug exists, was reported about five years ago, and was, at
the time, fixed.
So what I want to know:
Do I add a comment to the original bug report, even though that specific
instance of the bug was fixed?
Or do I create a new bug report, and reference the bug report where it
originally occurred?
What's tripping me up is that the bug was fixed, and the bug report is
therefore "closed." (I note that Inkscape doesn't actually seem to have a
"closed" status, but "fixed" seems to play the same role.)
On the one hand, adding a comment to the end of a fixed bug will prevent
duplication... but if it's "fixed," am I commenting on something no one
will
ever look at? On the other hand, creating a new bug report will ensure someone
looks at it, but am I just creating needless work for someone who is going to
have to close the report because it already exists?
Christopher B. Wright (wrightc@...537...)
------------------------------------------------------------------------------
Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
and more. Get SQL Server skills now (including 2012) with LearnDevNow -
200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only - learn more at:
http://p.sf.net/sfu/learnmore_122512
_______________________________________________
Inkscape-user mailing list
Inkscape-user(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-user
3975
days inactive
3975
days old
inkscape-user@lists.inkscape.org
5 comments
3 participants
participants (3)
-
Christopher B. Wright -
Frank Murphy -
Josh Andler