Archive:Proposal for testing builds - Revision history

Karellen: Karellen moved page Proposal for testing builds to Archive:Proposal for testing builds without leaving a redirect: random notes

2020-08-21T02:37:47Z

Karellen moved page Proposal for testing builds to Archive:Proposal for testing builds without leaving a redirect: random notes

← Older revision	Revision as of 02:37, 21 August 2020
(No difference)

NedBot: web link corrections for xbmc -> kodi

2015-05-13T00:51:57Z

web link corrections for xbmc -> kodi

← Older revision		Revision as of 00:51, 13 May 2015
Line 4:		Line 4:


	This is based off the format from: http://forum.~~xbmc~~.~~org~~/showthread.php?tid=107501		This is based off the format from: http://forum.kodi.tv/showthread.php?tid=107501


Line 63:		Line 63:

	Example:		Example:
	How to report issues on OSX: http://forum.~~xbmc~~.~~org~~/showthread.php?tid=47124		How to report issues on OSX: http://forum.kodi.tv/showthread.php?tid=47124

	You can include a statement about how your post will be deleted if you don't follow along:		You can include a statement about how your post will be deleted if you don't follow along:

NedBot: Bot: Automated text replacement (- XBMC + Kodi )

2015-05-04T08:48:54Z

Bot: Automated text replacement (- XBMC + Kodi )

← Older revision		Revision as of 08:48, 4 May 2015
Line 1:		Line 1:
	This is a proposal for a format that we can use to post builds to the forum for testing.		This is a proposal for a format that we can use to post builds to the forum for testing.

	In the hope of getting more testers and eyeballs testing ~~XBMC~~ features or bug fixes before they get into the main build, we would like to propose a format to post test builds to the forum so others can participate in troubleshooting and testing.		In the hope of getting more testers and eyeballs testing Kodi features or bug fixes before they get into the main build, we would like to propose a format to post test builds to the forum so others can participate in troubleshooting and testing.


Line 32:		Line 32:
	Download build at: http://blah		Download build at: http://blah
	backup Usedata from /Users/username/Library/Application Support/XBMC/Userdata. (ie, use Go>Goto Folder and input the path, replacing username with your username. Then go up one directory and copy the Userdata folder in another directory Or use cp in Terminal)		backup Usedata from /Users/username/Library/Application Support/XBMC/Userdata. (ie, use Go>Goto Folder and input the path, replacing username with your username. Then go up one directory and copy the Userdata folder in another directory Or use cp in Terminal)
	Run ~~XBMC~~ and make a note of what version you're using under System Info so you can roll back to it if needed.		Run Kodi and make a note of what version you're using under System Info so you can roll back to it if needed.
	Open up the DMG file and copy ~~XBMC~~ to Applications, overwriting existing.		Open up the DMG file and copy Kodi to Applications, overwriting existing.

	CAVEATS TO THIS BUILD:		CAVEATS TO THIS BUILD:

Ned Scott at 15:25, 12 October 2014

2014-10-12T15:25:41Z

← Older revision		Revision as of 15:25, 12 October 2014
Line 6:		Line 6:
	This is based off the format from: http://forum.xbmc.org/showthread.php?tid=107501		This is based off the format from: http://forum.xbmc.org/showthread.php?tid=107501


			== Formatting the test thread ==
	If you want multiple platforms tested, make posts in every sub-forum for each platform.		If you want multiple platforms tested, make posts in every sub-forum for each platform.

Keith: Created page with "This is a proposal for a format that we can use to post builds to the forum for testing. In the hope of getting more testers and eyeballs testing XBMC features or bug fixes ..."

2014-10-12T15:23:50Z

Created page with "This is a proposal for a format that we can use to post builds to the forum for testing. In the hope of getting more testers and eyeballs testing XBMC features or bug fixes ..."

New page

This is a proposal for a format that we can use to post builds to the forum for testing.

In the hope of getting more testers and eyeballs testing XBMC features or bug fixes before they get into the main build, we would like to propose a format to post test builds to the forum so others can participate in troubleshooting and testing.

This is based off the format from: http://forum.xbmc.org/showthread.php?tid=107501

If you want multiple platforms tested, make posts in every sub-forum for each platform.

'''SUBJECT:'''
Subject should be something that says the feature affected and that this is a testing build.

Example:
Subject: [AudioEngine] TEST BUILD! Testers needed to test out passthrough w/ DTS

'''BODY:'''

Start with Pre-reqs. This is a section that lists the requirements that are needed in order to be effective trying to use this build.

Example:

PRE-REQS: (or why to not use this build)
* OSX Platform, please list version when reporting
* Receiver that supports DTS

INSTRUCTIONS:
This is how to reproduce the issue that this hopefully fixes.

Example:
Download build at: http://blah
backup Usedata from /Users/username/Library/Application Support/XBMC/Userdata. (ie, use Go>Goto Folder and input the path, replacing username with your username. Then go up one directory and copy the Userdata folder in another directory Or use cp in Terminal)
Run XBMC and make a note of what version you're using under System Info so you can roll back to it if needed.
Open up the DMG file and copy XBMC to Applications, overwriting existing.

CAVEATS TO THIS BUILD:
These are stuff that isn't considered an issue yet, but might be affected, but should not be reported.

Example:
* DTS-HD may not work.

KNOWN ISSUES:
You probably don't need both this and Caveats, but in case you do.

Example:
Coax digital audio out isn't working.

NEEDS VERIFYING:
This is the most important section, which is what needs to be verified on this build.

Enabled:
* Enable DTS passthrough and test a file that supports DTS

REPORTING PROBLEMS:
Generically this is the info you should provide on reporting issues. If something specific is needed worked on, mention it.

Example:
Every initial report must include a .log link with debugging enabled. It's easy to tell now because when debugging is enabled theres 3 lines of txt across the screen.
If this is a media playback issue, you must run 'mediainfo' and cut up a sample of the file.

Include a link to report debugging problems on the specific platform you're using.

Example:
How to report issues on OSX: http://forum.xbmc.org/showthread.php?tid=47124

You can include a statement about how your post will be deleted if you don't follow along:

Example:

If you don't follow ANYTHING above, your post will be deleted.