From 32f665c56cfb26aeec38af52592c05efc7066552 Mon Sep 17 00:00:00 2001
From: Hui Lan <lanhui@zjnu.edu.cn>
Date: Mon, 13 Apr 2020 09:18:43 +0800
Subject: spm-slides.tex: pull version control and bug tracking.

---
 spm-slides.tex | 41 ++++++++++++++++++++++++++++++++++-------
 1 file changed, 34 insertions(+), 7 deletions(-)

(limited to 'spm-slides.tex')

diff --git a/spm-slides.tex b/spm-slides.tex
index 62d18d5..d18db3d 100644
--- a/spm-slides.tex
+++ b/spm-slides.tex
@@ -2213,15 +2213,15 @@ Thread support
 Searchability
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-\foilhead{Version (revision) control system}
+\foilhead{Version (revision) Control System}
 
 The core of version control is \underline{change management}: who made which change on which date.
 
-commit - make change to the project.  "I just committed a fix for the server crash bug people have been reporting on Mac OS X. Jay, could you please review the commit and check that I'm not misusing the allocator there?"
+{\bf commit} - make change to the project.  "I just committed a fix for the server crash bug people have been reporting on Mac OS X. Jay, could you please review the commit and check that I'm not misusing the allocator there?"
 
-push - publish a commit to a publicly online repository.
+{\bf push} - publish a commit to a publicly online repository.
 
-pull - pull others' changes (commits) into your copy of the project.
+{\bf pull} (or update) - pull others' changes (commits) into your copy of the project.
 
 commit message or log message -  commentary attached to each commit, describing the nature and purpose of the commit.
 
@@ -2229,6 +2229,8 @@ repository -  a database in which changes are stored and from which they are pub
 
 clone - obtain one's own development repository by making a copy of the project's central repository.  My fork.
 
+checkout - switch to a branch
+
 revision or  commit - "Oh yes, she fixed that in revision 10" or "She fixed that in commit fa458b1fac".
 
 diff - textual representation of a change.
@@ -2290,18 +2292,43 @@ Who made the change, when they made it, what files and directories changed, and
 Include the diff, set ``Reply-to'' to the regular development list.
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-\foilhead{Bug tracker}
+\foilhead{Bug Tracker}
+
+A bug tracker is more important and more useful that you might think.
+
+A first place to check a project's overall health.
 
 https://savannah.gnu.org/bugs/?53986
 
-Bug trackers can track non-bug information, e.g., new feature requests.
+https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908678
+
+A bug tracker can track non-bug information, e.g., new feature requests.
 
 The tracker is as much a public face of the project as the repository, mailing lists or web pages.
 
 Other names:  issue trackers, \underline{ticket} trackers, defect trackers, artifact trackers, request trackers.
 
-But Triage.
+Bug Triage.  Reproduce the bug.
+
+Invalid bug reports and  duplicate bug reports will increase the noise to signal ratio.
+
+Regression.  Fixed then re-appear.
+
+Bug life cycle.
+
+Bug severity: blocker, critical, major, normal, minor, trivial, enhancement.
+
+Bug importance: highest, high, normal, low, lowest.
+
+Bug state: open, unverified, diagnosed, confirmed, assigned, in progress, resolved (fixed, invalid, wontfix, duplicate worksforme), closed.
+
+It takes considerable time for people to report a bug.  Acknowledge each bug report with a timely response. 
+
+Interact with email.
+
+Respect anonymity.
 
+How to keep the bug tracker free of junk?  Buddy system:  ``Did you search the bug tracker to see if it's already been reported?''
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 % wed start here
-- 
cgit v1.2.1

