Re: "Closed" Radar Bugs not fixed?
Re: "Closed" Radar Bugs not fixed?
- Subject: Re: "Closed" Radar Bugs not fixed?
- From: Jeffrey Oleander <email@hidden>
- Date: Wed, 19 Sep 2012 16:23:33 -0700 (PDT)
And they stay "closed" regardless of what additional
screen images and other materials you add to show
that the problem persists.
It's a management issue.
> From: Owen Hartnett <email@hidden>
> Subject: Re: "Closed" Radar Bugs not fixed?
> To: "David Duncan" <email@hidden>
> Cc: "XCode Users" <email@hidden>
> Date: Tuesday, 2012 September 18, 18:54
> Just to follow up on this:
> I did refile the bug as 12300607. I got an
> email today saying it's a duplicate and is
> being tracked by duplicate
> radar 9320112, which is the
> same duplicate number as was attached to my
> original bug report, and it's still closed.
> So they twice marked my bug as duplicate
> indicating it's being tracked
> by bug 9320112, which is still closed.
> Unless I'm missing something, my bug report
> was an entire waste of not only my time, but
> the Apple Engineer who took whatever time
> he used to close it.
> All my bugs are marked duplicate, the
> duplicate bug is marked closed, which I
> assume is no further action needed or
> contemplated.
> I'm hoping you'll tell me I'm
> wrong.
> -Owen
> On Aug 13, 2012, at 7:08 PM, David Duncan
> <email@hidden>
> wrote:
> If you
> feel a bug is still not fixed, feel free to file a follow up
> bug, even referencing the previous bugs if you like. You
> already have the hard parts done – they are in the
> original report – no reason not to refile.
> On Aug 13, 2012, at 3:20 PM, Owen Hartnett <email@hidden>
> wrote:
> Yes. I
> realize this. But in my duplicate, Apple provides a
> display in radar of the status the original bug, which is
> marked as closed, though I can clearly test that it is not
> fixed. So, both bugs are marked closed, but the bug
> still exists in 4.4.1.
> So, my options are to refile a new bug (which
> does not seem like a good thing to do), or assume that Apple
> has investigated and will not fix, and ignore
> it.
> -Owen
> On Aug 13, 2012, at 10:12 AM, Alex Zavatone
> wrote:
> It's
> standard practice in QA to mark a dup bug as closed, even if
> the original bug is still open.
> This avoids creating an artificially high open
> bug count, as a bunch of open dups reports would do.
>
> On Aug 13, 2012, at 9:59 AM, Owen Hartnett
> wrote:
> Hi all:
> I have a bug in Xcode, I reported in May of 2011,
> which was marked as a duplicate, my radar 9379323,
> duplicate radar 9320112.
> The
> duplicate radar is marked as closed, but the bug, however,
> is not fixed. Should I consider that Apple has decided
> not to fix this bug, or that they believe it is fixed? The
> bug is still there in Xcode
> 4.4.1.
> -Owen
>
> This email sent to email@hidden
>
> This email sent to email@hidden
>
> --David
> Duncan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden