Reporting bugs/pl: Difference between revisions

From Miranda NG
Reporting bugs/pl
Jump to navigation Jump to search
(prepare for migration)
(Updating to match new version of source page)
Line 1: Line 1:
Chcemy tak samo jak Ty Mirandę wolną od błędów, więc pomóż nam pomóc sobie. Najważniejszą rzeczą do zapamiętania przy zgłaszaniu błędów jest dostarczenie '''pełnych''' i '''dokładnych''' informacji. Większość czasu spędzamy prosząc o ich uzupełnienie, aktualizację lub poprawiając je. Dlatego jeżeli chcesz zgłosić błąd, prosimy abyś zastosował się do poniższych instrukcji.
<languages/>
: '''Nasz bug tracker<nowiki>:</nowiki> https://github.com/miranda-ng/miranda-ng/issues'''
{{TNT|Important|
: (Możesz łatwo uzyskać do niego dostęp z menu Mirandy: {{Menu|Menu główne|Pomoc|Zgłoś błąd}}.)
* Please, make bug reports to our [https://github.com/miranda-ng/miranda-ng/issues issue tracker], so they won't get lost on forums or chatroom logs.<br>You can easily access it using Miranda: {{Menu|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 [https://forum.miranda-ng.org our forum] or [xmpp:miranda-ng-int@conference.jabber.ru?join chatroom] too.}}


== Przed zgłoszeniem błędu ==
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 {{Strong|complete}} and {{Strong|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.


* Zaktualizuj Mirandę do ostatniej {{GlossLink|Wersja rozwojowa|wersji rozwojowej}}. ([[Instalacja i aktualizacja#Aktualizowanie Mirandy NG|Aktualizowanie Mirandy NG]])
__TOC__
* Sprawdź czy błąd nadal występuje.
* Zorientuj się, w miarę możliwości, czy ten błąd nie został już zgłoszony. ([https://github.com/miranda-ng/miranda-ng/issues Zgłoszone błędy])


== Efektywne raportowanie błędów ==
== Before reporting a bug ==


Zrzut 1
* Update to the latest {{GlossLink|development version}} (see {{Ll|Installation and update#Updating Miranda NG|Updating Miranda NG}}).
* Check if the problem persists (it may happen that it has been fixed).
* Search the [https://github.com/miranda-ng/miranda-ng/issues issues] for an existing bug report for your problem.


Korzystanie z poniższych wskazówek może znacząco zwiększyć szanse na to, że Twój problem zostanie zauważony i szybko rozwiązany.
== Effective bug reporting ==
* Napisz dobre podsumowanie/temat zgłoszenia (Summary). (Jest to bardzo ważne gdyż nie możesz go później edytować.)
* Opisz problem jasno, w prostych słowach.
* Napisz, np. w punktach, krok po kroku jak odtworzyć problem. (Nie możemy naprawić czegoś, czego nie potrafimy odtworzyć.)
* Dołącz zrzuty ekranu jeżeli to możliwe. (Zrzuty dołączaj jako załączniki)
* Dołącz [[Informacje o wersji | Informacje o wersji (Version Info)]].
* Dołącz [[Raport awarii | Raport awarii (crashlog)]], w przypadku występowania awarii.
* Dołącz [[Raport połączeń | Raport połączeń (netlog)]], jeżeli występują problemy z łącznością.
* Określ inne elementy zgłoszenia, takie jak: priorytet (Priority), wagę defektu (Severity), komponent (Component) i wersję Mirandy (Version). Możesz także dodać słowa kluczowe (Keywords).


=== Jak dodać pliki do bugtrackera ===
[[File:Reporting bugs 01.png|200px|thumb|Screen 1: Creating issue]]


* Przed wciśnięciem ''"Create ticket"'', zaznacz opcję ''"I have files to attach"''. (Zrzut 1)
Using the following tips will greatly increase the chances of your issue being noticed and fixed quickly.
* Wciśnij ''"Browse"'', wybierz pliki jakie chcesz dodać i wciśnij ''"Add attachment"''. (Zrzut 2)


== Po zgłoszeniu problemu ==
* 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'').
* Attach screenshots if possible.
* Attach your {{Ll|Version information|VersionInfo}}.
* Attach a {{Ll|Crash reports|crash report}} if you are experiencing crashes (It includes VersionInfo as well).
* Attach a {{Ll|Network log|network log}} captured if you are experiencing connectivity issues.
* If Miranda freezes, hangs up or consumes CPU, attach {{Ll|Using Process Explorer as the debugging tool|information obtained by Process Explorer tool}}.


* Monitoruj swoje zgłoszenie.
=== How to attach files ===
* Dostarczaj odpowiedzi i dodatkowych informacji, w razie potrzeby.
 
* Nie sprzeczaj się czy coś jest błędem, czy nie.
* Attach files by dragging & dropping, selecting them, or pasting from the clipboard
* Press {{Button|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 [xmpp:miranda-ng-int@conference.jabber.ru?join 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.
 
== 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}}}}]]

Revision as of 21:21, 12 June 2018

Other languages:
Ważne
  • 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.

Before reporting a bug

Effective bug reporting

Screen 1: Creating issue

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

How to attach files

  • 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.

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.
Retrieved from "https://wiki.miranda-ng.org/index.php?title=Reporting_bugs/pl&oldid=31091"