If any part of the Takin project has bugs or documentation mistakes, please let us know by [Takin-issue]. We treat bugs and mistakes very seriously and believe no issue is too small, anyOne is implement. Before creating a bug report, please check that an issue reporting the same problem does not already exist.
To make the bug report accurate and easy to understand, please try to create bug reports that are:
-
Describe the bug. Include as much details as possible: which version, what environment, what configuration, etc. If the bug is related to running the Takin server, please attach the Takin log.
-
How to Reproducible. Include the steps to reproduce the problem. We understand some issues might be hard to reproduce, please includes the steps that might lead to the problem. If possible, please attach the affected Takin data and stack strace to the bug report.
-
Unique. Do not duplicate existing bug report.
It may be worthwhile to read Elika Etemad’s article on filing good bug reports before creating a bug report.
We might ask for further information to locate a bug. A duplicated bug report will be closed.
如果Takin项目存在任何问题，请通过[Takin-issue]告诉我们。我们会非常认真地对待缺陷或错误和缺陷或错误，我们相信在产品范围内没有任何不重要的问题。不过在创建缺陷或错误报告之前，请检查是否存在报告相同问题的issues。
为了使缺陷或错误报告准确且易于理解，请创建缺陷或错误报告尝试包含以下部分：
-
具体缺陷或错误细节。包括尽可能多的细节：哪个版本，什么环境，什么配置等。如果缺陷或错误与运行Takin服务有关，请附加Takin日志。
-
如何复现。包括重现问题的步骤。我们理解某些问题可能难以重现，请包括可能导致问题的步骤。如果可能，请将受影响的Takin数据和堆栈strace附加到缺陷或错误报告中。
-
缺陷或错误报告的唯一性。不要复制现有的缺陷或错误报告。
在创建缺陷或错误报告之前，最好阅读下[Elika Etemad关于提交好缺陷或错误报告的文章] [归档好缺陷或错误]，相信会帮助你更好的归档缺陷或错误。
我们可能会要求您提供更多信息以查找缺陷或错误。将关闭重复的缺陷或错误报告。