Differences between revisions 8 and 9
Revision 8 as of 2008-10-05 21:47:29
Size: 3225
Editor: FranklinPiat
Comment: reorgonise + add "Developpment system"
Revision 9 as of 2008-10-06 08:41:18
Size: 3761
Editor: FranklinPiat
Comment:
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
The four class of testers (risk) are equally useful to Debian. Classes depends on what situation you can recover your-self [[FootNote(How much time you can spend fixing a bug ; How often you want to backup, to recover potential data loss)]]. Each class of testers is very useful for Debian, since each different level test a different level of maturity of the Debian release. The four class of testers (risk) are equally useful to Debian. Classes depends on __what situation you can recover your-self__ [[FootNote(Risk = How much time you can spend fixing a bug ; How often you want to backup, to recover potential data loss)]]. Each class of testers is very useful for Debian, since each different level test a different level of maturity of the Debian release.
Line 19: Line 19:
 * Use ["KDE"] ''or'' ["Xfce"] desktops (you can install many and choose one when you login).
* Enable ["SELinux"][[FootNote(No SELinux is not considered harmful, but in some situation, but the default policy could prevent some program from working, and modifying )]] in "enforcing=0" mode, then report errors.
 * Enable ["SELinux"][[FootNote(No SELinux is not considered harmful, but in some situation, but the default policy could prevent some program from working. Understanding that a problem is due to SELinux isn't always obvious the [For those that don't check /var/log/syslog !)]] in "enforcing=0" mode, then report errors.
Line 23: Line 22:
 * Intel Core2 / AMD64 users : install Debian/i386 with both [wiki:DebPkg:linux-image-2.6-686 -686] and [wiki:DebPkg:linux-image-2.6-amd64 -amd64] kernels flavors, but use the later.  * Intel Core2 / AMD64 users : install Debian/i386 with both [wiki:DebPkg:linux-image-2.6-686 -686] and [wiki:DebPkg:linux-image-2.6-amd64 -amd64] kernels flavors, but use the later [[FootNote(users of Debian/i386 can switch from linux-image-2.6-amd64 to linux-image-2.6-686 kernels, in cases of problem.)]].
Line 36: Line 35:
 * Probably runs ["DebianTesting"].
 * Enable Dependency-based init systems ["LSBInitScripts"] (DebPkg:insserv).
 * Optionally, you can do some AptPinning of specific {{{unstable}}}'s packages.
 * Enable Dependency-based init systems ["LSBInitScripts"] (DebPkg:insserv) [[FootNote(The package insserv should be used with care, as incorrect or missing dependencies can lead to an unbootable system.)]]
 * Exceptionally, you can do some AptPinning of specific {{{backports}}}, {{{testing}}} or {{{unstable}}}'s packages (but keep in mind that you wouldn't get security updates this way).
 * ''Test'' system running ["DebianTesting"] falls in this category too.
Line 43: Line 42:
 * Have a ["DebianUnstable"] for development/test machine.
  * Check http://wiki.debian.org/TopicDebianDevel before updating each time
Line 47: Line 44:
 * ''Test'' systels running ["DebianUnstable"] falls in this category.
  * Reminder: Check ["TopicDebianDevel"] before updating ["DebianUnstable"], each time.
Line 48: Line 47:
== Development System == == DD Development System ==
Some system-wide features that are long term goals should be enabled on development systems.

[:DebianWiki/EditorGuide#translation:Translation(s)]: none

(!) [:/Discussion:Discussion]


Help Debian, by testing it and reporting bugs.

This pages lists some modificationd that you can make to your own (test) machine, in order to test some features (and report bugs!).

The four class of testers (risk) are equally useful to Debian. Classes depends on what situation you can recover your-self ?FootNote(Risk = How much time you can spend fixing a bug ; How often you want to backup, to recover potential data loss). Each class of testers is very useful for Debian, since each different level test a different level of maturity of the Debian release.

?TableOfContents(2)

. {i} Remember : ["Xen"], ["OpenVz"], [:QEMU:Qemu]... are your friends to run multiple system on a single machine.

No risk

This class is suitable to any user, running Debian on production machine.

  • Use/test any software from DebianStable and report bugs & problems.

  • (BTW, also submit documentation improvements : rephrase text, undocumented aspects, etc...).
  • Enable ["SELinux"]?FootNote(No SELinux is not considered harmful, but in some situation, but the default policy could prevent some program from working. Understanding that a problem is due to SELinux isn't always obvious the [For those that don't check /var/log/syslog !) in "enforcing=0" mode, then report errors.

  • Test Debian-Live CDs on various machines.
  • Test installing Debian on any machine you can.
  • Intel Core2 / AMD64 users : install Debian/i386 with both [wiki:linux-image-2.6-686 -686] and [wiki:linux-image-2.6-amd64 -amd64] kernels flavors, but use the later ?FootNote(users of Debian/i386 can switch from linux-image-2.6-amd64 to linux-image-2.6-686 kernels, in cases of problem.).

Medium risk

This class is suitable for Desktop/Laptop of advanced users.

  • Same as above, plus

  • Runs DebianStable, with ["StableProposedUpdates"] on your test machine.

  • Set dash as your /bin/sh

  • Enable ["SELinux"] in "enforcing=1" mode, switch to "enforcing=0" in case of problems.
  • Intel Core2 / AMD64 users : install Debian/amd64 distribution.

High risk

Advanced users may have a machine like this for development/test machine.

  • Same as above, plus

  • Enable Dependency-based init systems ["LSBInitScripts"] (insserv) ?FootNote(The package insserv should be used with care, as incorrect or missing dependencies can lead to an unbootable system.)

  • Exceptionally, you can do some AptPinning of specific backports, testing or unstable's packages (but keep in mind that you wouldn't get security updates this way).

  • Test system running ["DebianTesting"] falls in this category too.

Very-high risk

Debian Developers should have a test machine like this (typically in a [:SystemVirtualization:Virtual machine]).

  • Same as above, plus

  • Optionally, you can do some AptPinning of specific [:DebianExperimental:Experimental]'s packages.

    • like KDE4.1
  • Test systels running ["DebianUnstable"] falls in this category.

DD Development System

Some system-wide features that are long term goals should be enabled on development systems.

  • Enable ["SELinux"] (at least in "selinux=1 enforce=0", to collect errors).
  • Set dash as your [:BourneShell:/bin/sh] (to detect bashisms).

  • see other entries from the ["LennyReleaseGoals"] and ["SqueezeReleaseGoals"].