Bug Triage/pl

Dlaczego
Sortowanie błędów jest ważne, aby zorganizować i nadać priorytet błędom/funkcjom/patchom w odniesieniu do FreeCAD Bug Tracker. Jeśli to zadanie zostanie zaniedbane, projekt może ucierpieć z powodu tak zwanego "Bugtracker Bloat", który zasadniczo polega na gromadzeniu się i gniciu zaniedbanych zgłoszeń. Triage pomaga również zidentyfikować zduplikowane zgłoszenia, które mają tendencję do gromadzenia się, zwłaszcza jeśli istnieje długotrwały nierozwiązany problem, o którym zespół FC doskonale wie, ale z jakiegokolwiek powodu nie ma zasobów, aby go naprawić w danym momencie.



Jak segregować


Nowe
Zgodnie z dokumentacją MantisBTː

Innymi słowy, status NOWY wskazuje na kilka rzeczyː
 * 1) Zgłoszenie nie zostało potwierdzone.
 * 2) Zgłoszenie jest nadal w trakcie realizacji, tj. Triage / Devs nadal oceniają / wyjaśniają szczegóły zgłoszenia od OP.
 * 3) Zespół FreeCAD nie zdecydował jeszcze, co zrobić z tym zgłoszeniem.

Wszystkie aktualne otwarte zgłoszenia FreeCAD ze statusem NOWE.

Feedback
Tickets get designated this status when OP is being requested to provide more information.

The ticket is pending based on the participation of OP. For exampleː the ticket is missing FC version info; or perhaps a certain 3rd party library name or version is required etc... Devs need to set this status whenever replying to OP in order to indicate that the ticket is pending. This is important due to the possibilit that OP neglects to respond which has a high probability for the ticket to 'rot' in the tracker.

When OP responds the ticket status changes back to New automatically. Then ticket needs to be re-examined to decide what is needed.

Further discussion on this topic in the FreeCAD forum.

All current open FreeCAD tickets with FEEDBACK status in the FC bugtracker.

Confirmed
When a ticket is confirmed it has been eitherː It is now ready to be assigned to or by a dev.
 * a bug that has been reproduced
 * a feature that has been greenlit to be considered valid.

All current open FreeCAD tickets with CONFIRMED status in the FC tracker.

Assigned
Self-explanatory, these tickets that have been assigned to a specific developer.

All current open FreeCAD tickets with ASSIGNED status in the FC tracker.

Resolved
These tickets have been resolved but not closed yet, most likely because they need confirmation that the ticket has been fixed.

-

Open
Self-explanatory, all tickets remain as 'open' if they are still relevant at the discretion of the FC team.

Fixed
Tickets that have been fixed.

Unable to reproduce
Tickets deemed un-reproducible

Duplicate
Tickets that are or have a duplicate ticket.

No change required
Tickets were it has been ascertained that no modifications are necessary.

Won't fix
FC team has rejected the ticket request for whatever reason stated.

Reopened
Tickets that have been closed me then re-opened for a relevant reason. Most likely that the issue has resurfaced or wasn't totally fixed.

Tagging Tickets
An important methodology to track tickets by a certain subject/theme/category. It's important that Existing Tags be used to tag issues before new tags are created. If duplicate or superfluous tags are created the bug tracker admin is responsible to remove them and if possible retag said tickets.

Related
Bugtracker