Better bug tracking overview

Signed-off-by: Dan Scott <dan@coffeecode.net>

diff --git a/eg2012_ddd.txt b/eg2012_ddd.txt
index 74c0623..12ed996 100644 (file)
--- a/eg2012_ddd.txt
+++ b/eg2012_ddd.txt
@@ -7,14 +7,6 @@ Ecology of the Evergreen Developer
 :max-width: 45em
 :duration: 45
 
-One of the great assets of Evergreen is that its development community is
-readily accessible to anyone using it; accessible, that is, if you know how to
-find the Evergreen developers and speak their language! Feel comfortable
-participating in the world of Evergreen development by understanding what goes
-into making the product what it is, release by release, and take a tour of the
-processes, protocols, and standard tools employed by the Evergreen
-development community.
-
 The Release as the Central Artifact
 -----------------------------------
 (With apologies to MVLC, who proudly run the bleeding-edge version of
@@ -145,6 +137,8 @@ Anatomy of a git commit message
     the changeset and believes that it is ready to be part of the core
     repository
 
+
+
 What do developers do?
 ----------------------
   * Create Evergreen releases
@@ -198,17 +192,28 @@ Communicate - Launchpad
 -----------------------
   * Evergreen's third bug tracking system, following Bugzilla and Trac
     ** Also includes translation management support and some release management
-  * Bug workflow:
-    . Bugs are added to report bugs or to track the development of new features
-    . Testers attempt to reproduce a bug (`Confirmed`) and comment on their
-      testing environment and/or identify causes
-    . Developer creates a branch for a fix (or feature) and tags it
-      `pullrequest`
-    . Testers create signed-off branches
-    . When the branch is committed to the core repository, the bug is marked
-      `Fix committed`
-    . When the code is released in an official release, the bug is marked
-      `Fix released`
+  * Relatively easy to generate http://goo.gl/uMhdC[lists of open bugs] for a
+    given release series
+  * Pros:
+    ** Translations are seeded by strings from other projects
+    ** Requires no effort to host and maintain
+  * Some cons:
+    ** Version control system mismatch: Launchpad uses Bazaar, we use git
+    ** Locale name mismatch: Launchpad uses xx[_YY], Evergreen uses xx-YY
+
+Bug workflow
+------------
+  . Bugs are added to Launchpad to report actual bugs or to track the
+    development of new features
+  . Testers attempt to reproduce a bug (`Confirmed`) and comment on their
+    testing environment and/or identify causes
+  . Developer creates a branch for a fix (or feature) and tags it
+    `pullrequest`
+  . Testers create signed-off branches
+  . When the branch is committed to the core repository, the bug is marked
+    `Fix committed`
+  . When the code is released in an official release, the bug is marked
+    `Fix released`
  
 Communicate - Google Hangout
 ----------------------------
@@ -218,7 +223,8 @@ Communicate - Google Hangout
 
 Developer Glossary
 ------------------
-  * _*Tuits*_, or _*Round tuits*_ - a fictional device that would enable the
+  * _Tuits_, or _Round tuits_ - a fictional device that would enable the
     holder to accomplish all tasks that simply require time; as in "When I get
     around to it"
+  * _Reproducible test case_