我怎样才能让 Embarcadero Quality Central 对我的错误报告采取措施

发布于 2024-08-08 06:57:12 字数 724 浏览 5 评论 0原文

大约一年前,我在 SO 上问了这个问题: 菜单加速键未显示(Delphi 2009)

StackOverflow 的程序员给出的答案非常出色,在 16 小时内,我就得出结论,这是 Delphi 2009 VCL 中的错误,而 Delphi 4 中不存在。

所以当时我在 Embarcadero 的质量中心,报告 # 68816,标题为:“菜单加速键未显示向上”。

我给了它“严重/高度可见的问题”的严重性,我认为我在描述中进行了详细说明,甚至给出了返回 StackOverflow 问题的链接,他们可以在其中获取更多信息和屏幕截图。

大约两个半星期后,内河码头的某人注意到了这一点,在决议评论中添加的评论是“已升级到内部数据库”。

我不确定“内部数据库”是什么 - 可能是一个错误存储库 - 但这根本没有告诉我错误报告的状态是什么,因为现在已经过去 10 个月了,而且没有任何迹象表明我的错误报告的状态是什么。进展正在发生。该问题的状态仍为“开放”,其解决方案仍列为“无”。

我想以某种方式提高此错误报告的紧迫性。我该怎么做?

It's almost a year ago that I asked this question on SO:
Menu Accelerator Keys Not Showing Up (Delphi 2009)

The Delphi programmers here at StackOverflow were superb with their answers, and within 16 hours, I was able to conclude that this was a bug in the VCL of Delphi 2009 that was not there in Delphi 4.

So at that time I reported it on Embarcadero's Quality Central, Report # 68816 with the title: "Menu Accelerator Keys Not Showing Up".

I gave it a Severity of "Serious / Highly visible problem", and I think I was detailed in the description, even giving a link back to the StackOverflow question where they could get more info and screen shots.

It was noticed by someone at Embarcadero about two and a half weeks later, and under the Resolution Comments the comment added was that it was "Promoted to internal database".

I'm not sure what the "internal database" is - probably a bug repository - but that does not tell me at all what the status of my bug report is, since it is now over 10 months later and there is no indication of any progress happening at all. The status of the question is still "open" and its resolution is still listed as "None".

I would like to elevate the urgency of this bug report somehow. How can I do this?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

梦归所梦 2024-08-15 06:57:12

该错误在内部数据库中被标记为“高”。对于 bug 有两个更高优先级的设置 - Must Fix(粗略地说,应该在下一个版本中修复)和 WUpdate(应该在下一个更新中修复) - 所以看起来,在 VCL 的 QA 人员的判断中,有更高的优先级优先级错误。

尽管我是一名员工,但我是开发人员,所以我通常不会直接处理客户服务请求。提高 bug 优先级的最佳方法可能是让很多人对其进行投票,并且通常说服产品领域社区 beta 测试人员将其包含在其最高优先级 bug 列表中。

The bug is marked "High" in the internal database. There are two higher priority settings for bugs - Must Fix (roughly, should be fixed for next release) and WUpdate (should be fixed for next update) - so it appears that in the judgement of the QA folks for the VCL, there are higher priority bugs.

Even though I'm an employee, I'm on the development side, so I generally don't deal with customer service requests directly. Probably the best way of raising the bug's priority is having lots of people vote on it, and generally convincing the product area community beta tester leads to include it in their highest priority bug lists.

意犹 2024-08-15 06:57:12

首先帮助你:在这个问题得到解决之前,你可以做一个拦截器类。请参阅此处了解详细信息。基本上,您必须将 Delphi 2009 的单元复制到您的目录中,并使用 Delphi 4 中的旧源代码(如果有的话)更改有问题的部分 - diff 工具在这里会有所帮助 - 和/或通过阅读 Microsoft 的文档。

并回答您的问题标题:

  1. 在 Embarcadero 论坛中制造噪音并寻找选票:.non-technical & .qualitycentral 是最合适的。但不要交叉发帖。
  2. 提供解决方案并将其包含在您的报告中。 (在体内 - 如果小 - 作为附件如果大)

First to help you: Till this will get fixed, you can do an interceptor class. See here for details. Basically you must copy the Delphi 2009's unit in your directory and change the problematic part using the old source from Delphi 4 (if you have it) - a diff tool would help here - and/or by reading the Microsoft's documentation.

And to answer to the title of your question:

  1. Make noise and hunt for votes in Embarcadero's forums: .non-technical & .qualitycentral are the most appropriate. But don't cross-post.
  2. Provide a solution and include it in your report. (In the body - if is small - as attachment if is big)
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文