Difference between revisions of "Bug tracker"

From Official Kodi Wiki
Jump to: navigation, search
m
 
(15 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{DevsHeader|'''XBMC Bug tracker'''}}<br />
+
{{mininav|[[Development]]|[[Troubleshooting]]}}
  
{{cleanup}}
+
{{divbox|red||'''Note:''' As per DevCon 2018, you can no longer use the bug tracker at http:/trac.kodi.tv for entering new tickets.
  
No software project the size and scope of XBMC has any hope of being successful without a bug tracker to keep things organized.  Team XBMC has chosen [http://trac.edgewall.org trac]for this task because of it's feature set, ease of use, flexibility and expandability.  Though mainly a tool for developers, there are a few features that the inquisitive user might find interesting as well.
+
New issues are now to be submitted via Kodi's [https://github.com/xbmc/xbmc/issues Github Tracker]
 +
}}
  
==Submitting bug reports==
+
No software project the size and scope of Kodi has any hope of being successful without a bug tracker to keep things organized. ''[[Team Kodi]]'' has chosen [https://github.com/xbmc/xbmc/issues GitHub] to be able to show issues for outside developers. Currently almost no one follows what happens on trac.kodi.tv, and things tend to simply get buried over time. Though mainly a platform for developers, there are a few things that the inquisitive user might find interesting as well.
 +
 
 +
== Submitting bug reports ==
 
{{see also|HOW-TO:Submit a bug report}}
 
{{see also|HOW-TO:Submit a bug report}}
  
==What is the bug tracker?==
+
== What is the Github-Issue tracker? ==
The [http://trac.xbmc.org bug tracker] is an organizational tool for developers used to keep tabs on issues within the project.  It provides a one stop shop for all current XBMC activity.  Whether you're looking for the latest commit messages, keeping an eye on that pesky bug that's been bothering you in the latest release or just want to get an idea of what the team has planned for the future, the bug tracker is your spot.
+
The [https://github.com/xbmc/xbmc/issues GitHub Tracker] is an organizational tool for developers used to keep tabs on issues within the project.  It provides a one stop shop for all current Kodi activity.  Whether you're looking for the latest commit messages, keeping an eye on that pesky bug that's been bothering you in the latest release or just want to get an idea of what the team has planned for the future, GitHub is your spot.
 +
 
 +
== What isn't the bug tracker? ==
 +
The [https://github.com/xbmc/xbmc/issues issue tracker] is '''not''' a support channel.  The tickets are business-only.  There's no need for "me too" or "bump" comments.  If you don't have some new technical information on the issue, feel free to CC yourself and keep an eye on it.  Maybe you will later.<br />
 +
If you think you've found a bug, but aren't a software developer, please follow the guide for [[HOW-TO:Submit_a_bug_report]].  This is to cut down on superfluous tickets for issues that can be resolved by some of our friendly users, letting the team focus on confirmed problems.
  
==What isn't the bug tracker?==
+
== Features ==
The [http://trac.xbmc.org bug tracker] is '''not''' a support channel. The tickets are business-only.  There's no need for "me too" or "bump" comments. If you don't have some new technical information on the issue, feel free to CC yourself and keep an eye on itMaybe you will later.<br>
+
=== Commits ===
If you think you've found a bug, but aren't a software developer, please follow the guide for [[Reporting_problems|reporting problems]].  This is to cut down on superfluous tickets for issues that can be resolved by some of our friendly users, letting the team focus on confirmed problems.
+
The [https://github.com/xbmc/xbmc/commits/master Commits] lists all of the changes which made their way into the Kodi source code. They are separated by branch. So you are still able to follow what happens in the past and what will happen in the furtureAll of you obsessive users won't be able to live without this one.
  
==Features==
+
=== Browse Source ===
===Timeline===
+
The [https://github.com/xbmc/xbmc source browser] lets developers take a peek under the hood without digging out all of the usual toolsIt's especially nice for viewing differences between changesets without fiddling in SCM.  Not to mention quickly figure out who to blame for that bug you just fixed. ;)
The [http://trac.xbmc.org/timeline timeline] keeps a play by play account of every commit to the source tree as well as when each ticket or milestone opens or closeAll of you obsessive users won't be able to live without this one.
 
  
===Roadmap===
+
=== Pull Requests ===
{{notice|1=During XBMC v12 development, Team XBMC switched from Trac roadmap/milestones to using Github milestones: https://github.com/xbmc/xbmc/issues/milestones?state=open}}
 
The [http://trac.xbmc.org/roadmap roadmap] is where the achievements of past milestones, goals of future milestones and progress of the current milestone live.  If you're unsure of whether XBMC supports some feature, this is a good place to start looking.
 
  
===Browse Source===
+
[https://github.com/xbmc/xbmc/pulls GitHub Pull requests] are showing every suggestions, fixes, improvements, features etc. our contributors and developers are offering to Kodi to make the best out of the project. If you have an improvement or are able to fix some bug reported at the issues, please feel free to submit your own PR.  
The [http://trac.xbmc.org/browser source browser] lets developers take a peek under the hood without digging out all of the usual tools. It's especially nice for viewing differences between changesets without fiddling in SCM.  Not to mention quickly figure out who to blame for that bug you just fixed. ;)
 
  
===View Tickets===
+
=== View Tickets ===
The [http://trac.xbmc.org/report ticket browser] gives you access to all tickets, both open and closed.  There are several predefined sort methods as well as a plethora of sort criteria to cook your own.
+
The [https://github.com/xbmc/xbmc/issues ticket/issue browser] gives you access to all actual tickets and issues, both open and closed.  There are several predefined sort methods as well as a plethora of sort criteria to cook your own.
  
===New Ticket===
+
=== New Ticket ===
This one is pretty self explanatory.  Make sure to provide as much detail about the issue as possible, fill out the submission fields accurately and follow the guide for [[HOW-TO_submit_a_proper_Bug_Report|submitting bugs]].
+
This one is pretty self explanatory.  Make sure to provide as much detail about the issue as possible, fill out the submission fields accurately and follow the guide for [[HOW-TO submit a proper Bug Report|submitting bugs]].
  
==See also==
+
== See also ==
*[[HOW-TO:Submit a bug report]]
+
* [[HOW-TO:Submit a bug report]]
*[[Log file]]
+
* [[Log file]]
*[[Troubleshooting]]
+
* [[Troubleshooting]]
 +
{{Helix updated}}
  
 
[[Category:Trac|*]]
 
[[Category:Trac|*]]
 
[[Category:Development]]
 
[[Category:Development]]
 +
[[Category:Troubleshooting]]

Latest revision as of 15:03, 11 October 2018

Home icon grey.png   ▶ Development ▶ Troubleshooting ▶ Bug tracker

No software project the size and scope of Kodi has any hope of being successful without a bug tracker to keep things organized. Team Kodi has chosen GitHub to be able to show issues for outside developers. Currently almost no one follows what happens on trac.kodi.tv, and things tend to simply get buried over time. Though mainly a platform for developers, there are a few things that the inquisitive user might find interesting as well.

1 Submitting bug reports

2 What is the Github-Issue tracker?

The GitHub Tracker is an organizational tool for developers used to keep tabs on issues within the project. It provides a one stop shop for all current Kodi activity. Whether you're looking for the latest commit messages, keeping an eye on that pesky bug that's been bothering you in the latest release or just want to get an idea of what the team has planned for the future, GitHub is your spot.

3 What isn't the bug tracker?

The issue tracker is not a support channel. The tickets are business-only. There's no need for "me too" or "bump" comments. If you don't have some new technical information on the issue, feel free to CC yourself and keep an eye on it. Maybe you will later.
If you think you've found a bug, but aren't a software developer, please follow the guide for HOW-TO:Submit_a_bug_report. This is to cut down on superfluous tickets for issues that can be resolved by some of our friendly users, letting the team focus on confirmed problems.

4 Features

4.1 Commits

The Commits lists all of the changes which made their way into the Kodi source code. They are separated by branch. So you are still able to follow what happens in the past and what will happen in the furture. All of you obsessive users won't be able to live without this one.

4.2 Browse Source

The source browser lets developers take a peek under the hood without digging out all of the usual tools. It's especially nice for viewing differences between changesets without fiddling in SCM. Not to mention quickly figure out who to blame for that bug you just fixed. ;)

4.3 Pull Requests

GitHub Pull requests are showing every suggestions, fixes, improvements, features etc. our contributors and developers are offering to Kodi to make the best out of the project. If you have an improvement or are able to fix some bug reported at the issues, please feel free to submit your own PR.

4.4 View Tickets

The ticket/issue browser gives you access to all actual tickets and issues, both open and closed. There are several predefined sort methods as well as a plethora of sort criteria to cook your own.

4.5 New Ticket

This one is pretty self explanatory. Make sure to provide as much detail about the issue as possible, fill out the submission fields accurately and follow the guide for submitting bugs.

5 See also