请帮我翻译这篇文章!
The status and resolution fields define and track the life cycle of a bug.
The status field indicates the general health of a bug. Only certain status transitions are allowed.
UNCONFIRMED
This bug has recently been added to the database. Nobody has validated that this bug is true. Users who have the "canconfirm" permission set may confirm this bug, changing its state to NEW. Or, it may be directly resolved and ed RESOLVED.
NEW
This bug has recently been added to the assignee's list of bugs and must be processed. Bugs in this state may be accepted, and become ASSIGNED, passed on to someone else, and remain NEW, or resolved and ed RESOLVED.
ASSIGNED
This bug is not yet resolved, but is assigned to the proper person. From here bugs can be given to another person and become NEW, or resolved and become .
REOPENED
This bug was once resolved, but the resolution was deemed incorrect. For example, a bug is REOPENED when more information shows up and the bug is now reproducible. From here bugs are either ed ASSIGNED or .
RESOLVED
A resolution has been taken, and it is awaiting verification by QA. From here bugs are either re-opened and become REOPENED, are ed , or are closed for good and ed CLOSED.
VERIFIED
QA has looked at the bug and the resolution and agrees that the appropriate resolution has been taken. Bugs remain in this state until the product they were reported against actually ships, at which point they become CLOSED.
CLOSED
The bug is considered dead, the resolution is correct. Any zombie bugs who choose to walk the earth again must do so by becoming REOPENED.
The resolution field indicates what happened to this bug.
No resolution yet. All bugs which are in one of these "open" states have the resolution set to blank. All other bugs will be ed with one of the following resolutions.
FIXED
A fix for this bug is checked into the tree and tested.
INVALID
The problem described is not a bug.
WONTFIX
The problem described is a bug which will never be fixed.
DUPLICATE
The problem is a duplicate of an existing bug. Marking a bug duplicate requires the bug# of the duplicating bug and will at least put that bug number in the description field.
WORKSFORME
All attempts at reproducing this bug were futile, and reading the code produces no clues as to why the described behavior would occur. If more information appears later, the bug can be reopened.
MOVED
The problem was specific to a related product whose bugs are tracked in another bug database. The bug has been moved to that database.
Severity
This field describes the impact of a bug.
Blocker Blocks development and/or testing work
Critical crashes, loss of data, severe memory leak
Major major loss of function
Minor minor loss of function, or other problem where easy workaround is present
Trivial cosmetic problem like misspelled words or misaligned text
Enhancement Request for enhancement
Priority
This field describes the importance and order in which a bug should be fixed. This field is utilized by the programmers/engineers to prioritize their work to be done. The available priorities range from P1 (most important) to P5 (least important.)
Platform
This is the hardware platform against which the bug was reported. Legal platforms include:
• All (happens on all platforms; cross-platform bug)
• Macintosh
• PC
• Sun
• HP
Note: When searching, selecting the option "All" does not select bugs assigned against any platform. It merely selects bugs that are ed as occurring on all platforms, i.e. are designated "All".
Operating System
This is the operating system against which the bug was reported. Legal operating systems include:
• All (happens on all operating systems; cross-platformbug)
• Windows 95
• Mac System 8.0
• Linux
Sometimes the operating system implies the platform, but not always. For example, Linux can run on PC and Macintosh and others.
Assigned To
This is the person in charge of resolving the bug. Every time this field changes, the status changes to NEW to make it easy to see which new bugs have appeared on a person's list.
The default status for queries is set to NEW, and REOPENED. When searching for bugs that have been resolved or verified, remember to set the status field appropriately.
The status and resolution fields define and track the life cycle of a bug.
The status field indicates the general health of a bug. Only certain status transitions are allowed.
UNCONFIRMED
This bug has recently been added to the database. Nobody has validated that this bug is true. Users who have the "canconfirm" permission set may confirm this bug, changing its state to NEW. Or, it may be directly resolved and ed RESOLVED.
NEW
This bug has recently been added to the assignee's list of bugs and must be processed. Bugs in this state may be accepted, and become ASSIGNED, passed on to someone else, and remain NEW, or resolved and ed RESOLVED.
ASSIGNED
This bug is not yet resolved, but is assigned to the proper person. From here bugs can be given to another person and become NEW, or resolved and become .
REOPENED
This bug was once resolved, but the resolution was deemed incorrect. For example, a bug is REOPENED when more information shows up and the bug is now reproducible. From here bugs are either ed ASSIGNED or .
RESOLVED
A resolution has been taken, and it is awaiting verification by QA. From here bugs are either re-opened and become REOPENED, are ed , or are closed for good and ed CLOSED.
VERIFIED
QA has looked at the bug and the resolution and agrees that the appropriate resolution has been taken. Bugs remain in this state until the product they were reported against actually ships, at which point they become CLOSED.
CLOSED
The bug is considered dead, the resolution is correct. Any zombie bugs who choose to walk the earth again must do so by becoming REOPENED.
The resolution field indicates what happened to this bug.
No resolution yet. All bugs which are in one of these "open" states have the resolution set to blank. All other bugs will be ed with one of the following resolutions.
FIXED
A fix for this bug is checked into the tree and tested.
INVALID
The problem described is not a bug.
WONTFIX
The problem described is a bug which will never be fixed.
DUPLICATE
The problem is a duplicate of an existing bug. Marking a bug duplicate requires the bug# of the duplicating bug and will at least put that bug number in the description field.
WORKSFORME
All attempts at reproducing this bug were futile, and reading the code produces no clues as to why the described behavior would occur. If more information appears later, the bug can be reopened.
MOVED
The problem was specific to a related product whose bugs are tracked in another bug database. The bug has been moved to that database.
Severity
This field describes the impact of a bug.
Blocker Blocks development and/or testing work
Critical crashes, loss of data, severe memory leak
Major major loss of function
Minor minor loss of function, or other problem where easy workaround is present
Trivial cosmetic problem like misspelled words or misaligned text
Enhancement Request for enhancement
Priority
This field describes the importance and order in which a bug should be fixed. This field is utilized by the programmers/engineers to prioritize their work to be done. The available priorities range from P1 (most important) to P5 (least important.)
Platform
This is the hardware platform against which the bug was reported. Legal platforms include:
• All (happens on all platforms; cross-platform bug)
• Macintosh
• PC
• Sun
• HP
Note: When searching, selecting the option "All" does not select bugs assigned against any platform. It merely selects bugs that are ed as occurring on all platforms, i.e. are designated "All".
Operating System
This is the operating system against which the bug was reported. Legal operating systems include:
• All (happens on all operating systems; cross-platformbug)
• Windows 95
• Mac System 8.0
• Linux
Sometimes the operating system implies the platform, but not always. For example, Linux can run on PC and Macintosh and others.
Assigned To
This is the person in charge of resolving the bug. Every time this field changes, the status changes to NEW to make it easy to see which new bugs have appeared on a person's list.
The default status for queries is set to NEW, and REOPENED. When searching for bugs that have been resolved or verified, remember to set the status field appropriately.
解决方案 »
- 驱动:IRP异步完成 StartIO - IoStartPacket 问题??again...
- 我想要一个能实现计算机与单片机通讯的程序,请各位帮帮忙啊
- 请教如何将内存中的一个html格式的字符串显示在htmlview中,谢谢!!!
- 问一个白痴问题:怎样使我的程序与数据库连接起来呀?
- 请问如何改变tabctrl的背景
- 操作符重载问题。
- WORD的一小BUG,巨有意思!
- 一个新手的问题.言者有分
- 求方法:要求双击目录打开之前能启动自己的程序进行目录的检查,
- 关于建立.dll文件
- 怎么修改vc6.0里面.cpp文件里面代码的字体,和字体颜色?
- 关于clistctrl控件的问题,能不能我存数据的时候不自动更新!
大概的意思就是bug分成n个状态
重要程度分为n级p1到p5
要标明bug发生的hardware platform 硬件平台和软件平台
最后是附加的两个原则