Reporting bugs/be: Difference between revisions

From Miranda NG
Reporting bugs/be
Jump to navigation Jump to search
(Imported translation using page migration)
(Updating to match new version of source page)
 
(5 intermediate revisions by 2 users not shown)
Line 14: Line 14:
* Пераканаецеся, што на [https://github.com/miranda-ng/miranda-ng/issues трэкеры] няма паведамлення пра вашу памылку.
* Пераканаецеся, што на [https://github.com/miranda-ng/miranda-ng/issues трэкеры] няма паведамлення пра вашу памылку.


{{Anchor|Effective bug reporting}}
== Паведамленне пра памылку ==
== Паведамленне пра памылку ==


Line 20: Line 21:
Using the following tips will greatly increase the chances of your issue being noticed and fixed quickly.
Using the following tips will greatly increase the chances of your issue being noticed and fixed quickly.


<div class="mw-translate-fuzzy">
* Have a well-written bug Title field – describe the issue clearly, in simple words.
* Provide step-by-step instructions in Description field  so we can reproduce the issue (''We can't fix what we can't reproduce'').
* Зрабіце і прыкладзіце здымак экрана.
* Зрабіце і прыкладзіце здымак экрана.
* Стварыце і прыкладзіце {{Ll|Version information|VersionInfo}}.
* Стварыце і прыкладзіце {{Ll|Version information|VersionInfo}}.
* Калі Міранда «падае», стварыце і прыкладзіце {Ll|Crash reports|краш-рэпарт}} (утрымоўвае таксама VersionInfo).
* Калі Міранда «падае», стварыце і прыкладзіце {{Ll|Crash reports|краш-рэпарт}} (утрымоўвае таксама VersionInfo).
* Калі ў вас праблемы з далучэннем, стварыце і прыкладзіце {{Ll|Network log|сеткавы лог}}.
* Калі ў вас праблемы з далучэннем, стварыце і прыкладзіце {{Ll|Network log|сеткавы лог}}.
</div>
* If Miranda freezes, hangs up or consumes CPU, attach {{Ll|Using Process Explorer as the debugging tool|information obtained by Process Explorer tool}}.


=== How to attach files ===
=== Як прыкласці файл ===


* Attach files by dragging & dropping, selecting them, or pasting from the clipboard
* Attach files by dragging & dropping, selecting them, or pasting from the clipboard
Line 41: Line 43:
Then you can try to reproduce your problem on each of them and find out when exactly it got broken. With that info it's easy to reach out the developer who commited the broken commit and ask him to look at it.
Then you can try to reproduce your problem on each of them and find out when exactly it got broken. With that info it's easy to reach out the developer who commited the broken commit and ask him to look at it.


== After reporting an issue ==
== Што рабіць потым ==


* Monitor the issues you report.
* Сачыце за сваім паведамленнем.
* Provide feedback and additional information if requested.
* Адказвайце на пытанні і падавайце дадатковую інфармацыю.
* Don't argue about whether something is a bug or not.
* Не спрачайцеся, з'яўляецца ваша праблема памылкай ці не.


[[Category:Help|{{#getdisplaytitle:{{FULLPAGENAME}}}}]]
[[Category:Help{{#translation:}}|{{#getdisplaytitle:{{FULLPAGENAME}}}}]]

Latest revision as of 11:09, 13 June 2018

Other languages:
Важнае
  • Please, make bug reports to our issue tracker, so they won't get lost on forums or chatroom logs.
    You can easily access it using Miranda: Main menu → Help → Report bug.
  • If you are unsure about the problem or want to bring more attention to it, you can mention it on our forum or chatroom too.

We want Miranda as bug free as you do, so help us help you. The most important thing to remember when reporting bugs is to provide complete and accurate information. Most of our time is spent asking for more information and fixing/updating information. So if you report a bug, please take the time to read and follow these recommendations.

З чаго пачаць

Паведамленне пра памылку

Мал. 1

Using the following tips will greatly increase the chances of your issue being noticed and fixed quickly.

Як прыкласці файл

  • Attach files by dragging & dropping, selecting them, or pasting from the clipboard
  • Press Submit new issue (see Screen 1).

I know when it got broken

If you know things got broken in some version or at some particular time, then it's good because you can try different releases from different revisions and narrow down where exactly the problem started to happen:

  • You can either compile the revisions yourself (that requires more knowledge and time).
  • Or ask someone in our jabber conference to help you identify potentially problematic revisions and then ask to compile those revisions for you.

Then you can try to reproduce your problem on each of them and find out when exactly it got broken. With that info it's easy to reach out the developer who commited the broken commit and ask him to look at it.

Што рабіць потым

  • Сачыце за сваім паведамленнем.
  • Адказвайце на пытанні і падавайце дадатковую інфармацыю.
  • Не спрачайцеся, з'яўляецца ваша праблема памылкай ці не.