Red Hat Bugzilla介绍
Thank you for visiting Red Hat Bugzilla. Red Hat Bugzilla is the Red Hat bug-tracking system and is used to submit and review defects that have been found in Red Hat distributions. Red Hat Bugzilla is not an avenue for technical assistance or support, but simply a bug tracking system. If you submit a defect, please provide detailed information in your submission after you have queried Red Hat Bugzilla to ensure the defect has not been reported yet. Defects will go directly to the engineer responsible for the component you filed the defect against. Engineers have many responsibilities and will get to your defect in due time.
Bug Writing Guidelines故障编写指南
https://bugzilla.redhat.com/page.cgi?id=bug-writing.html
Effective bug reports are the most likely to be fixed. These guidelines explain how to write such reports.
1) Principles原则
a) Be precise准确
b) Be clear清楚 - explain it so others can reproduce the bug
c) One bug per report每个报告一个故障
d) No bug is too trivial to report不要因为故障小而不上报 - small bugs may hide big bugs小故障可能隐藏着大故障
e) Clearly separate fact from speculation将事实与推测明确分开
2) Preliminaries初步措施
a) 使用最新版本是否能复现您的故障，如果可以的话建议升级最新版本Reproduce your bug using a recent build of the software, to see whether it has already been fixed.
b) 从Red Hat Bugzilla搜索，查看是否是已知故障。Search Red Hat Bugzilla, to see whether your bug has already been reported.
3) Reporting a New Bug上报故障
If you have reproduced the bug in a recent build and no-one else appears to have reported it, then:
a) Choose "Enter a new bug"
b) Select the product in which you've found the bug
c) Fill out the form. Here is some help understanding it:
c.1) Component: In which sub-part of the software does it exist?
This field is required. Click the word "Component" to see a description of each component. If none seems appropriate, look for a "General" component.
c.2) OS: On which operating system (OS) did you find it? (e.g. Linux, Windows XP, Mac OS X.)
If you know the bug happens on more than one type of operating system, choose All. If your OS isn't listed, choose Other.
c.3) Summary故障描述(60个字符内): How would you describe the bug, in approximately 60 or fewer characters?
A good summary should quickly and uniquely identify a bug report. It should explain the problem, not your suggested solution.
Good好的例子: "Cancelling a File Copy dialog crashes File Manager"取消文件复制对话框会使文件管理器崩溃”
Bad不好的例子: "Software crashes"软件崩溃
Bad不好的例子: "Browser should work with my web site"浏览器应与我的网站一起使用
c.4) Description: The details of your problem report, including:
Overview概况: More detailed restatement of summary.
Drag-selecting any page crashes Mac builds in the NSGetFactory function.
Version-Release number of selected component (if applicable)组件版本号: The version number of the component that is causing this problem. For example if you were experiencing a problem with the grep command in RHEL 6, the component version would be 2.6.3.
How reproducible是否能够复现: Can this bug always be reproduced, or only reproduced occasionally.
always
Steps to Reproduce复现的步骤: Minimized, easy-to-follow steps that will trigger the bug. Include any special setup steps.
1) View any web page. (I used the default sample page, resource:/res/samples/test0.html)
2) Drag-select the page. (Specifically, while holding down the mouse button, drag the mouse pointer downwards from any point in the browser's content region to the bottom of the browser's content region.)
Actual Results实际结果: What the application did after performing the above steps.
The application crashed.
Expected Results期望结果: What the application should have done, were the bug not present.
The window should scroll downwards. Scrolled content should be selected.
(Or, at least, the application should not crash.)
Build Date & Hardware编译的时间和所在硬件设备: Date and hardware of the build in which you first encountered the bug.
Build 2006-08-10 on Mac OS 10.4.3
Additional Builds and Platforms在其它平台有没有故障: Whether or not the bug takes place on other platforms (or browsers, if applicable).
Doesn't Occur On Build 2006-08-10 on Windows XP Home (Service Pack 2)
Additional Information其它有用信息: Any other useful information.
For crashing bugs:
Windows: Note the type of the crash, and the module that the application crashed in (e.g. access violation in apprunner.exe).
Mac OS X: Attach the "Crash Reporter" log that appears upon crash. Only include the section directly below the crashing thread, usually titled "Thread 0 Crashed". Please do not paste the entire log!
Double-check your report for errors and omissions, then press "Commit". Your bug report will now be in the Red Hat Bugzilla database.
Red Hat Bugzilla 使用指南user guide
https://bugzilla.redhat.com/docs/en/html/using/index.html
使用前先创建一个账号，如何填写一个故障，如何理解一个故障，如何编辑一个故障，如何搜索找到一个故障。
来看下详细的BUG单内容
https://bugzilla.redhat.com/show_bug.cgi?id=624293
1) Description of problem
2) Version-Release number of selected component (if applicable)
see sosreport
3) How reproducible
4) Steps to Reproduce
4.1)
4.2)
4.3)
5) Actual results
6) Expected results
7) Additional info
How should i proced with this error?
thanks Michael
总结：可借鉴的
1) 学习了故障编写的原则，自己提了那么多故障，怎么没有提出来故障编写的原则?是否可以开发出自己的一套原则?
2) 如何编写一个故障：需要填写哪些信息
3) 初步认识了一个故障单跟踪系统Bugzilla
点击自己之前使用jira的心得回顾对比下。
网友评论