From 455052ac3bc1e3e5e454f023efcb9b48f3c9d38b Mon Sep 17 00:00:00 2001
From: "harrison%netscape.com" <>
Date: Tue, 27 Oct 1998 18:43:38 +0000
Subject: updates for collectstats.pl and the Chart::Base requirement

---
 README | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)

(limited to 'README')

diff --git a/README b/README
index 5af19d61e..c24bc96b0 100644
--- a/README
+++ b/README
@@ -24,8 +24,9 @@ this document!)
 First, you need some other things:
 
    1) MySQL database server.
-   2) Perl5.004 or greater, including MySQL support and the Date::Format
-      package from CPAN.
+   2) Perl5.004 or greater, including MySQL support, and modules
+	    Date::Format and Chart::Base available from your nearest
+			CPAN server. See http://www.perl.com/CPAN.
       ftp://ftp.cpan.org/pub/CPAN/authors/id/GBARR/TimeDate-1.08.tar.gz
    3) Some kind of HTTP server so you could use CGI scripts
 
@@ -63,7 +64,7 @@ bugs database. You may have to hack the code to use "nobody"
 or whatever your HTTP server is running as.
 
 
-2. TWEAKING THE TOOLS
+2. Tweaking the Tools
 
   All scripts look in /usr/bonsaitools/bin for perl. Make 
 the appropriate links or modify the paths in each script.
@@ -129,3 +130,12 @@ That file gets automatically regenerated whenever it's more than an
 hour old, so Bugzilla will eventually notice your changes by itself,
 but generally you want it to notice right away, so that you can test
 things.
+
+
+7. Optional: Bug Graphs
+
+Place collectstats.pl in your crontab once/day to take a snapshot
+of the number of open, assigned and reopened bugs for every 
+product. The tool will create a data/mining directory and append 
+the count to a file named for the product. After at least two points 
+of data are available, you can view a graph from the Bug Reports page. 
-- 
cgit v1.2.3-65-gdbad