Bug tracker - Revision history

Karellen at 06:32, 12 July 2020

2020-07-12T06:32:43Z

← Older revision		Revision as of 06:32, 12 July 2020
Line 6:		Line 6:
	}}		}}

	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.		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 ==		== Submitting bug reports ==
	{{see also\|HOW-TO:~~Submit a bug report~~}}		{{see also\|HOW-TO:Submit_a_bug_report}}

	== What is the Github-Issue tracker? ==		== What is the Github-Issue tracker? ==
Line 33:		Line 33:

	=== 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_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}}		{{Helix updated}}

	~~[[Category:Trac\|*]]~~
	[[Category:Development]]		[[Category:Development]]
	[[Category:Troubleshooting]]		[[Category:Troubleshooting]]

Klojum at 15:03, 11 October 2018

2018-10-11T15:03:12Z

← Older revision		Revision as of 15:03, 11 October 2018
Line 1:		Line 1:
	{{mininav\|[[Development]]\|[[Troubleshooting]]}}		{{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.

			New issues are now to be submitted via Kodi's [https://github.com/xbmc/xbmc/issues Github 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 [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.		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.

Davu at 21:20, 9 October 2018

2018-10-09T21:20:07Z

← Older revision		Revision as of 21:20, 9 October 2018
Line 3:		Line 3:
	{{cleanup}}		{{cleanup}}

	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 [~~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.		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 ==		== 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~~.~~kodi.tv 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.		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? ==		== What isn't the bug tracker? ==
	The [~~http~~://~~trac~~.~~kodi.tv 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.<br />		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 [[~~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.		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.

	== Features ==		== Features ==
	=== ~~Timeline~~ ===		=== Commits ===
	The [~~http~~://~~trac~~.~~kodi.tv~~/~~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 close~~. All of you obsessive users won't be able to live without this one.		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 furture. All of you obsessive users won't be able to live without this one.

	=== Browse Source ===		=== Browse Source ===
	The [https://github.com/xbmc/xbmc 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. ;)		The [https://github.com/xbmc/xbmc 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. ;)

			=== Pull Requests ===

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

	=== View Tickets ===		=== View Tickets ===
	The [~~http~~://~~trac~~.~~kodi.tv~~/~~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 ===

NedBot: web link corrections for xbmc -> kodi

2015-05-13T00:39:50Z

web link corrections for xbmc -> kodi

← Older revision		Revision as of 00:39, 13 May 2015
Line 9:		Line 9:

	== What is the bug tracker? ==		== What is the bug 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 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.		The [http://trac.kodi.tv 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? ==		== What isn't the bug tracker? ==
	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 it. Maybe you will later.<br />		The [http://trac.kodi.tv 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.<br />
	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.		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.

	== Features ==		== Features ==
	=== Timeline ===		=== Timeline ===
	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 close. All of you obsessive users won't be able to live without this one.		The [http://trac.kodi.tv/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 close. All of you obsessive users won't be able to live without this one.

	=== Browse Source ===		=== Browse Source ===
Line 23:		Line 23:

	=== 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 [http://trac.kodi.tv/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.

	=== New Ticket ===		=== New Ticket ===

Davu at 08:19, 13 April 2015

2015-04-13T08:19:09Z

← Older revision		Revision as of 08:19, 13 April 2015
Line 3:		Line 3:
	{{cleanup}}		{{cleanup}}

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

	== Submitting bug reports ==		== Submitting bug reports ==
Line 9:		Line 9:

	== What is the bug tracker? ==		== What is the bug 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 [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 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? ==		== What isn't the bug tracker? ==
Line 32:		Line 32:
	* [[Log file]]		* [[Log file]]
	* [[Troubleshooting]]		* [[Troubleshooting]]
	{{~~Frodo~~ updated}}		{{Helix updated}}

	[[Category:Trac\|*]]		[[Category:Trac\|*]]
	[[Category:Development]]		[[Category:Development]]
	[[Category:Troubleshooting]]		[[Category:Troubleshooting]]

NedBot: Robot: Substituting template: Name

2014-06-05T20:18:54Z

Robot: Substituting template: Name

← Older revision		Revision as of 20:18, 5 June 2014
Line 3:		Line 3:
	{{cleanup}}		{{cleanup}}

	No software project the size and scope of ~~{{name}}~~ 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.		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.

	== Submitting bug reports ==		== Submitting bug reports ==
Line 9:		Line 9:

	== What is the bug tracker? ==		== What is the bug 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 ~~{{name}}~~ 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 [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.

	== What isn't the bug tracker? ==		== What isn't the bug tracker? ==

NedBot: Bot: Automated text replacement (- XBMC + {{name}} )

2014-06-05T01:00:50Z

Bot: Automated text replacement (- XBMC + {{name}} )

← Older revision		Revision as of 01:00, 5 June 2014
Line 3:		Line 3:
	{{cleanup}}		{{cleanup}}

	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.		No software project the size and scope of {{name}} 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.

	== Submitting bug reports ==		== Submitting bug reports ==
Line 9:		Line 9:

	== What is the bug tracker? ==		== What is the bug 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 [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 {{name}} 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? ==		== What isn't the bug tracker? ==

Ned Scott at 06:43, 7 September 2013

2013-09-07T06:43:02Z

← Older revision		Revision as of 06:43, 7 September 2013
Line 1:		Line 1:
	{{mininav\|[[~~General topics~~]]\|[[Troubleshooting]]}}		{{mininav\|[[Development]]\|[[Troubleshooting]]}}


	~~<br />~~

	{{cleanup}}		{{cleanup}}

Martijn: /* Browse Source */

2013-09-04T20:41:44Z

Browse Source

← Older revision		Revision as of 20:41, 4 September 2013
Line 23:		Line 23:

	=== Browse Source ===		=== Browse Source ===
	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. ;)		The [https://github.com/xbmc/xbmc 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 ===

Martijn at 08:15, 2 September 2013

2013-09-02T08:15:27Z

← Older revision		Revision as of 08:15, 2 September 2013
Line 1:		Line 1:
			{{mininav\|[[General topics]]\|[[Troubleshooting]]}}


	<br />		<br />