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

What is the bug tracker?
The 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 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, the bug tracker is your spot.

What isn't the bug tracker?
The 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 it. Maybe you will later.

If you think you've found a bug, but aren't a software developer, please follow the guide for 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.

Timeline
The timeline keeps a play by play account of every commit to the source tree as well as when each ticket or milestone opens or close. All of you obsessive users won't be able to live without this one.

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. ;)

View Tickets
The 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.

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.