r179 - /web/deps/dep10.mdwn

[seanius at users.alioth.debian.org]

Author: seanius
Date: Sun May  1 17:09:33 2011
New Revision: 179

URL: http://svn.debian.org/wsvn/dep/?sc=1&rev=179
Log:
DEP-10: add some example use cases in the release methods

Modified:
    web/deps/dep10.mdwn

Modified: web/deps/dep10.mdwn
URL: http://svn.debian.org/wsvn/dep/web/deps/dep10.mdwn?rev=179&op=diff
==============================================================================
--- web/deps/dep10.mdwn (original)
+++ web/deps/dep10.mdwn Sun May  1 17:09:33 2011
@@ -81,12 +81,17 @@
 	.-.-.-.-: Release targeted activity.  Freezes and limited uploads. 
 	\ \ \ \ : Package migration activity.
 
+### Use cases with `frozen`
 
-### Benefits with the `frozen` method
+Users were divided into two sets, those using `unstable` and those using
+`stable`.  Very few users would use both, as the two lines of development
+would quickly diverge from each other.
+
+### Benefits with `frozen`
 
  * Work in unstable continued, unaffected by the freeze.
 
-### Problems with the `frozen` method
+### Problems with `frozen`
 
  * Release work started from a buggy suite.
  * Duplicated effort in unstable/frozen.
@@ -127,13 +132,28 @@
 some extent frozen from non-release activity for many packages, since
 it still serves as the main route to testing for new uploads.
 
-### Benefits with the testing method
+### Use cases with `testing`
+
+The introduction of the new suite also introduced a type of continuum
+in which users now have more flexibility in selecting what to have installed.
+
+ * `unstable`: only the "bleeding edge" of Debian updates.
+ * `testing`: only the "leading edge" of Debian updates.
+ * `testing/unstable`: A hybrid solution of the two previous use cases,
+    allowing for a reasonable balance between them.
+ * `stable`: The latest stable release.
+ * `stable/testing`: the stable release with perhaps some newer packages
+    installed, typically also making use of "APT pins" to prevent unwanted
+    upgrades.  Less common now with the inclusion of backports and volatile
+	as official Debian services.
+
+### Benefits with the `testing`
 
  * Release branch has far fewer bugs at the start of the release process.
  * (Ideally) shorter release process with fewer problems.
  * Large user-base for testing stable-targeted fixes.
 
-### Problems with the testing method
+### Problems with `testing`
 
 (See [Introduction](#introduction))