Writing a good Enhancement Request
Writing a good Enhancement Request
- Subject: Writing a good Enhancement Request
- From: Scott Anguish <email@hidden>
- Date: Fri, 14 May 2004 03:12:36 -0400
I've been guilty of harping on folks to write enhancement requests, as
well as filing bug reports.
So let me give some guidelines that might make those enhancement
requests more useful.
- Provide as much information as possible.
Be explicit about what you want and what you'd like to see. Don't
just say "Please add support for SOMEFORMATIMAGE to AppKit." Instead
say which classes it would be a useful addition to, and why.
- Provide information about how this feature impacts your application.
If your application would benefit greatly from (or be hurt by the
lack of) a feature, include those details in the radar. How you'd use
it, what you'd be able to implement, etc..
- Point to any public resources
If you know where the file format for SOMEFORMATIMAGE lives, add a
pointer to it.
- Describe your application
We can assume that a bug filed by some well known Mac company is
about one of their apps, but not everyone is a well known Mac company.
If you can provide a brief description of what your app does, if it's
related to the bug, then it can't hurt.
Finally,
Don't be discouraged if it's closed as a Duplicate.
Your bug _was_ important too, but someone else got there before you.
However, even if it's closed, the bug will still be related to the
original, and duplicates help Apple know where there is demand for
features. Your request still carries weight.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.