Wiki page report_bugs changed with summary [] by Raster

This commit is contained in:
Carsten Haitzler 2015-06-22 20:02:28 -07:00 committed by apache
parent e21e8c3ca8
commit 1ba2b95efe
1 changed files with 13 additions and 13 deletions

View File

@ -4,7 +4,7 @@
* Be precise
* Be clear
* Only one bug a report
* Only report a bug in https://phab.enlightenment.org/maniphest/task/create/
* Only report a bug [[https://phab.enlightenment.org/maniphest/task/create|here]]
* Read what you wrote
=== Before reporting ===
@ -17,12 +17,12 @@ make sure you have not changed a setting somewhere and know the way to get it.
//**__Has someone else already reported the issue?__**//
Check on https://phab.enlightenment.org/maniphest/query/all/ if your bug has
Check [[https://phab.enlightenment.org/maniphest/query/all|here]] if your bug has
already been reported, if not you can report it.
//**__Where to report the bug?__**//
Only report a bug in https://phab.enlightenment.org/maniphest/task/create/.\\
Only report bugs [[https://phab.enlightenment.org/maniphest/task/create|here]].
Don't send bug reports and patches to the Enlightenment mailing list, bugs
will be lost. If there is more discussion needed add a bug report before or
after the discussion on the mailing list.
@ -33,7 +33,7 @@ If reporting a visual bug, make absolutely sure you test with the default
theme. EFL developers do not support other themes, and bug related to other
themes must be sent directly to the theme's author.
//**__Are there a lot of traces of valgrind,gdb,etc for your bug?__**//
//**__Are there a lot of traces of Valgrind, GDB, etc. for your bug?__**//
If there is a ton of output traces, please attach them as file uploads. And go
check in [[/debugging/apps_efl_debugging|Application EFL Debugging]] and
@ -42,17 +42,17 @@ information.
=== Reporting bugs ===
- Go to https://phab.enlightenment.org/maniphest/task/create/
- Go [[https://phab.enlightenment.org/maniphest/task/create|here]]
- Fill out at least the following fields:
* Title: A short one-sentence summary that explains the problem clearly and precisely.
* Assigned to: Ignore it, developers will set an assignee.
* CC: Ignore it or if you know interested users you can add them.
* Priority: Ignore it, set by developers.
* Select the project(s) in which you find the bug.
* Title: A short one-sentence summary that explains the problem clearly and precisely
* Assigned to: Ignore it, developers will set an assignee
* CC: Ignore it or if you know interested users you can add them
* Priority: Ignore it, set by developers
* Select the project(s) in which you find the bug
* Description :
- The way for reproducing the bug step by step: Minimized, easy-to-follow steps that will trigger the described problem.
- The way for reproducing the bug step by step: Minimized, easy-to-follow steps that will trigger the described problem
- Actual results: What the program errors are, the log traces (if it is not too long)
- Expected results: what the program should have done if there was no bug.
- Expected results: what the program should have done if there was no bug
- Additional information
- To attach a log or screenshot, etc, click on the Upload File button in the tool bar of description field.
- Read again what you wrote and create task.
- Read again what you wrote and create task