2012年9月,Bugzilla所取代JIRA。 你可以使用你的ReactOS网站登录凭证。 几个字段都是一样的,如果你有问题关于文件错误,请使用论坛。


第一步

如果你认为你发现一个错误在ReactOS:

  • 确保你可以复制你的错误。 重启ReactOS并再试一次,以确保。

  • 检查还没有报道。 JIRA搜索会帮你证实了这一点。

  • 确保你正在测试一种最近和官方ReactOS构建。 新构建(优先测试源)在这里

  • 如果您正在运行ReactOS虚拟机,请注意,我们的支持QEMU,VMwareVirtualBox。 其他人不支持。

由于某些错误类型项目的范围,请:

  • 不报告建立刀具磨损在公共平台上(Windows、Linux)。 这些在IRC或请报告邮件列表

  • 不报告功能宣布下一个版本的Windows(WinFS等等)。

  • 不报告bug在外部组件(Freetype、酒、台面等)。 请使用其他项目的bug追踪器。

重要的信息包括

以确保我们可以复制和修复bug,某些信息必须在场。 重要的数据应该包括在你的报告包括:

  • 繁殖方法使用一步一步指令。

  • 硬件或虚拟机配置。

  • ReactOS测试版本(验证也确实发生每夜构建

  • 测试版本的应用程序(如果有的话)和一个下载链接(URL)。

  • 截图的问题如果是一个图形化的bug(JIRA添加附件)。

  • 调试日志崩溃、死机和应用程序错误。 看到调试如何获得高质量的调试输出。

报告指南

为了缓解bug报告和修复,请遵循这些指导方针:

  • 选择一个简洁的错误标题。

  • 将调试日志文件附加到错误报告,而不是粘贴。 这提高了报告的可读性。

  • 附加图片JIRA直接而不是使用外部主机服务。

  • 使用JIRA文件错误,不是寻求支持或讨论事情相关的bug。

  • 错误报告一个问题,即使它发生在多个应用程序或以多种方式可以被复制。

  • 一个错误报告的职位只有一个问题。

报告违反这些准则将关闭无效的和记者将被要求报告错误。

如果任何问题或关于bug报告过程出现问题,咨询AmineKhaldi Caemyr或gabriel_it IRC(消失了)。




In September 2012, Bugzilla was replaced by JIRA. You can log in using your ReactOS website credentials. Several fields are the same as before, if you have questions regarding filing bugs, please use forum.

Contents

1 Procedure

1.1 First Steps

1.2 Important Information to Include

1.3 Reporting Guidelines

Procedure

This page describes how to file bugs in our JIRA Bug-Tracking Software. JIRA is used in this project to gather information about failing or misbehaving components and allows us to coordinate bug fixing efforts.

First Steps

If you think you found a bug in ReactOS:

Make sure you can replicate your bug. Restart ReactOS and try again to make sure.

Check that it hasn't been reported already. The JIRA search will help you confirm this.

Make sure you are testing a recent and official ReactOS build. New nightly builds (preferred testing source) can be obtained here.

If you are running ReactOS on a virtual machine, please mind that we support QEMU, VMware and VirtualBox. Others are not supported.

Since certain bug types are out of the scope of the project, please:

Do not report build breakages on common platforms (Windows, Linux). Please report these on IRC or to the mailing list.

Do not report features announced for the next version of Windows (WinFS, etc.).

Do not report bugs in external components (Freetype, Wine, Mesa, etc.). Please use the other project's bug trackers for this purpose.

Important Information to Include

To make sure we can reproduce and fix your bug, certain information has to be present. Important data you should include in your report includes:

Reproduction method using step by step instructions.

Hardware or virtual machine configuration.

Tested ReactOS version (verify also that it does happen on nightly builds.

The version of the application tested (if any) and a download link (URL).

Screenshot of the problem if it's a graphical bug (add the attachment in JIRA).

Debug log for crashes, freezes and application errors. See Debugging to see how to obtain a high quality debug output.

Reporting Guidelines

To ease bug reporting and fixing, please follow these guidelines:

Choose a concise bug title.

Attach the debug log file to the bug report, instead of pasting it in.  This improves the report's readability.

Attach pictures to JIRA directly instead of using external hosting services.

Use JIRA to file bugs, not to ask for support or discuss things not related to the bug.

Cover a single problem in the bug report, even if it happens in multiple applications or can be replicated in multiple ways.

Post only one issue in a single bug report.

Reports that violate these guidelines will be closed as invalid and the reporter will be asked to report the bug properly.

If any questions or problems regarding the bug reporting process arise, consult AmineKhaldi, Caemyr or gabriel_it(gone) on IRC.