Re: Radar issues (Re: How to file a radar)
Re: Radar issues (Re: How to file a radar)
- Subject: Re: Radar issues (Re: How to file a radar)
- From: Ben Weiss <email@hidden>
- Date: Wed, 19 Jul 2006 12:58:22 -0700
Speaking of duplicates, I have some bugs filed on Radar that are
undoubtedly duplicates, and yet aren't listed as such. Given that
duplicate bugs get higher priority to fix, I would hope the
duplication would be noted and logged.
For example: radar #4566275, the fact that rectangular text block
copy/paste is broken in XCode. (I believe this is actually a Cocoa
bug.) I'm still constantly jumping back and forth to Codewarrior to
edit rectangular blocks of code, and it drives me nuts.
The lack of support for separate debug/release libraries is another
major headache. I worked with some Apple engineers to hack around
this at the last WWDC, and I'm surprised it hasn't been addressed yet...
Optimistically hoping for some magically good stuff at WWDC!
Ben
On Jul 19, 2006, at 8:35 AM, Laurence Harris wrote:
On Jul 19, 2006, at 7:54 AM, Finlay Dobbie wrote:
On 19/07/06, Markus Hitter <email@hidden> wrote:
Am 19.07.2006 um 07:12 schrieb Chris Espinosa:
> The time to influence product content is every day, and this
forum,
> xcode-feedback, and bugreporter do an excellent job of it.
IMHO, small changes in Radar's public interface could improve
acceptance of Radar a lot.
Add to these:
- ability to see the bug report that yours duplicates.
I don't think this one is ever going to happen, if only to ensure
that confidential information isn't made available (even
accidentally) to other developers. A lot of bug reports give some
insight into what a product does and a lot of developers want to
keep that stuff private.
or at least its title and status.
I think duplicates should be treated like an original when it comes
to notification of the resolution. If 100 people file the same bug,
it makes no sense to me to only notify the person who filed the
first report and only ask him to confirm that it's fixed.
In addition to the obvious reasons for notifying everyone who
reported a bug, what if some of those duplicates aren't really
duplicates? I filed a radar on an interface issue in an Apple
application one time and got a response back suggesting I should
use some Cocoa API to display an alert (I have no idea what they
were smoking that day). So clearly some reports are "misfiled." If
a bug is closed as a duplicate because someone at Apple didn't read
it correctly, it's just lost.
Larry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40benweiss.com
This email sent to email@hidden
_______________________________________________
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