On Sep 23, 2008, at 7:56 AM, Rick Schummer wrote:
> I agree it is a poor design to have a string too long error when you
> UPPER() a memo field. Calling
> it a bug is easy, but it might not fit the true definition of a bug.
Thanks. This is exactly the sort of weasel-wording that developers
hate from any vendor about their product. And while your exhaustive
explanations may be technically correct, they still leave a bad
impression.
> So Ed, how do you approach this with the Dabo Frameworks and Tools?
> Do you call all bug reports or
> developer perceptions of incorrect behavior bugs?
I probably go to the opposite extreme: unless there is a clear case
that the reporter is not using it correctly, it's a bug. Sometimes
it's a matter of documentation that's out of date; sometimes it's a
case of different expectations; sometimes it's simply a bug.
If you're really curious, and not just being defensive about MS,
every post on dabo-users is archived just like every post on ProFox:
http://leafe.com/archives/search/dabo-users
You can also view our Trac site for bug/issue tracking:
http://trac.dabodev.com/report
Go through these, and see how reports are handled. If you find a case
of either Paul or me being dismissive about a report, please point it
out.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
