Testing and Working

Getting Started

TODO: This section needs more detail and more work. Everything on this page also needs review by someone on the Ubuntu Platform Team.

Welcome to the wonderful world of Ubuntu testing. This guide will help you avoid common pitfalls of running an Ubuntu developmental release. Some guidelines:

Getting Help

General

"Living on the Edge" can sometimes involve debugging problems, asking for help and filing bug reports if you encounter problems.

Specific

Mirror Problems

Uninstallable packages

Unpack failures

Configure Options

Package system debugging

Incorrect removals

Administrative error

Crashes during upgrades

Hardware-specific breakage

Kernel breakage

X.org breakage

Network breakage

Unpredictable bugs

Remote upgrades

Comments

I concur as well. When examinig the forums I found that people who were testing the development releases were new and in-experienced with testing. It should be noted that as time goes on more and more people will be turning towards Ubuntu and so in-experienced users will be answering more questions than before. An information database of some sort should be compiled such that a tester or inexperineced person can use it to report a problem.

For example: One tester for Karmic said "I installed Karmic update and now I have no sound. What should I try to do?"

The information database would very much help in this respect by telling the person to type: lspci|grep -i audio which would display hardware info. In addition it would also check to see if mute is enabled as some updates/releases cause programs to set to mute when not expected.

I.E. at the end of the day it would be nice to have a database of commands which a tester should know in order to figure out or fix his problem. In-experienced people find it difficult to come to terms with commands they dont know or have never heard of before. nolanking <<Saturday, October 17 2009: 01:12)>>


CategoryUbuntuDevelopment

UsingDevelopmentReleases/FixingProblems (last edited 2010-10-01 13:14:39 by p4FCE5C7F)