Hacking:How To Report Valentina Bugs: Difference between revisions
m
Update URL, rebranding
(Marked this version for translation) |
m (Update URL, rebranding) |
||
(4 intermediate revisions by 3 users not shown) | |||
Line 1:
<languages /><br />
<translate>
== How To Report
If you find a bug or think you find a bug, it is very important to report it. If the developers don’t know it is broken (or might be broken), they can’t fix it. So there you are at your computer trying to do something with
=== What is Issue Tracker? === <!--T:10-->
Line 10 ⟶ 11:
<!--T:3-->
Next: Go away and yell and scream and do whatever you need to do to relax again. Your next step will be to brave [https://
<!--T:4-->
Third: Check to see if your bug has been reported yet. Go to the [https://
=== Getting Ready to Report and Reporting a Bug === <!--T:5-->
Line 19 ⟶ 20:
==== The Steps ==== <!--T:6-->
# Use <code>
# Attempt to reproduce the problem. Go do what you were doing when it happened and see if you can do it again.
#:If using
#:To narrow down the exact cause of the problem, attempt to reproduce it in other ways. Prepare yourself to explain how to reproduce it in your bug report. If you are running
# Prepare to face the horror. Go to the Seamly2D github repo [https://
# Select “Create issue”. This opens the actual entry form.
# Here you have to tell the developers everything about your system, your version of
##For “Title”, write a brief description of your bug. This title will help other users see if their bug might be like your bug. Write something that would help you if you were looking for a bug like yours.
##“Description” is the hard part. It is the actual bug report. First provide the detailed description of your bug: a brief overview of when it happened and exactly what went wrong (including error messages). Next, describe step-by-step how to reproduce the bug. Use the exact name of menu items. Describe tools, windows, and clicks as precisely as possible. If they can’t reproduce the bug, it will be very hard for them to fix it. Last, tell them anything else you can think of that might be relevant. This could include recently installed programs or hardware that might interfere with
##Leave “Assignee” blank.
##Classify the “Kind” of your report. If you found a bug you should select "bug". You "enhancement" if you know how to make
##Classify the “Priority” of your bug. If the bug causes
##Select the appropriate “component”. If you don’t know what component it is, submit the bug under General. Descriptions of the components are [[Describe components|available]].
##Leave “Milestone” blank.
Line 43 ⟶ 44:
=== The Wait Patiently Part === <!--T:9-->
Whee!! You survived! If you managed to get through all this and submit your bug report, be happy. Be proud. You will later get e-mails about your bug. It might include a request for more information. If you get something that says your bug is not a bug, do not be discouraged from reporting in the future. Next time it might be. Submitting careful bug reports and providing additional information where possible helps make
</translate>
|