From e88fcdc8d999da5f81b97ca22714b3a741d8e536 Mon Sep 17 00:00:00 2001
From: Simon J Mudd <sjmudd@pobox.com>
Date: Tue, 24 Feb 2015 07:53:24 +0100
Subject: [PATCH] bump version to 0.3.4 and adjust copyright for 2015

---
 BUGS               | 30 ------------------------------
 NEW_FEATURES       | 23 +++++++----------------
 lib/common.go      |  2 +-
 version/version.go |  2 +-
 4 files changed, 9 insertions(+), 48 deletions(-)

diff --git a/BUGS b/BUGS
index eb9a34a..8d0cc9c 100644
--- a/BUGS
+++ b/BUGS
@@ -11,33 +11,3 @@ hard-coded stuff which matches personal usage.
 compressed connection to speed things up, but that is not possible
 at the moment. See https://github.com/go-sql-driver/mysql/issues/24
 for more details.
-
-3. Sometimes I see this:
-
-pstop 0.0.12 -  8:46:41 xxxxxxxxxxxxx / 5.6.21-log, up 1d 22h 59m 16s   [ABS]
-Latency by Table Name (table_io_waits_summary_by_table) 239 rows
-Table Name                        Latency      %| Fetch Insert Update Delete
-xxx.xxxxxxxx                    5124.10 h +++.+%|100.0%
-xxxxxx.xxxxxxxxxxxx             5124.10 h +++.+%|100.0%
-xxxxxx.xxxxxxx                  5124.10 h +++.+%|100.0%
-xxxxxxxx.xxxxxxxxxx             5124.09 h +++.+%|100.0%
-xxxxxxxx.xxxxxxxx               5124.09 h +++.+%|100.0%
-xxxxxx.xxxx                      00:07:49  49.2%| 98.6%   0.3%          1.1%
-xxxxxxxxx.xxxxxxxxxxx            00:06:23  40.2%| 97.4%   2.4%          0.1%
-xxxxxxxxx.xxxxxxxxxx              26.25 s   2.8%|114.2%   0.1% +++.+%   0.0%
-xxxxxx.xxxxxxxx                   15.71 s   1.6%| 99.6%   0.4%
-
-with a very long latency. Related to doing backups. Need to check the cause
-of the 5124.10h ++ issue. Probably a subtraction problem of some sort.
-
-4. Mutex page needs to configure P_S and restore confiuration on exit.
-
-This is: set the appropriate settings such as
-
-UPDATE setup_instruments
-SET enabled = 'YES', timed = 'YES'
-WHERE NAME LIKE 'wait/synch/mutex/innodb/%';
-
-However, on exit, it should restore the previous settings back to
-what they were before.  Currently if you've not set p_s appropriately you
-won't get any useful information out of this page.
diff --git a/NEW_FEATURES b/NEW_FEATURES
index 6ca2b5a..1d4cf6a 100644
--- a/NEW_FEATURES
+++ b/NEW_FEATURES
@@ -4,42 +4,33 @@ New features
 Some thoughts for new features which I hope to get around to.
 See also BUGS which probably need fixing first.
 
-1. performance_schema has several tables showing a wide variety of
-interesting information. So look and see which tables are most
-interesting and adapt pstop to show this.
-
-2. Often we want to look at behaviour over time when we change
-something, so cumulative statistics are not idea: we'd like to see
+1. Often we want to look at behaviour over time when we change
+something, so cumulative statistics are not ideal: we'd like to see
 a window of data which gradually moves over time. Look at how to
 implement this with ps_top.  I'd expect the window to be rather
 small, perhaps 1 minute, or maybe longer triggered by collecting
 data less frequently.
 
-3. vmstat, iostat, pt-diskstats and other such utilities show values
+2. vmstat, iostat, pt-diskstats and other such utilities show values
 over time but providing output as stdout. It might be useful to
 have options to pstop to present the info in that sort of format
 too.
 
-4. Add some replication metrics to pstop as most of my servers are
+3. Add some replication metrics to pstop as most of my servers are
 slaves and we want to know where the server is busy. I've seen a
 way to do that and need to incorporate it into pstop.
 
-5. _if_ ps statistics get truncated it would be good to be able to
+4. _if_ ps statistics get truncated it would be good to be able to
 remember the latest state and add those metrics back again, _if_
 looking at absolute rather than relative statistics. On servers I
 manage I currently truncate info as it is collected after 15-minutes,
 so this might happen while watching a server with pstop.
 
-6. Improve the options for sorting the data. Total latency is good,
+5. Improve the options for sorting the data. Total latency is good,
 but it would be good to see the write based metrics ordered by total
 write latency. So look to improve the display and sort options here.
 
-7. Add command line options for providing access to the MySQL server.
---defaults-file=/path/to/.my.cnf now works, but missing an explicit
---host=xx --port=99 --user=xx --password=xx or --socket=/path/to/mysql.sock
-options.
-
-8. I/O Latency by File shows read/write bytes and operations but
+6. I/O Latency by File shows read/write bytes and operations but
 none of these values is converted into B/s or ops/sec which might
 be better given we want to see the rate values.  MB/s or ops/s are
 easier to understand and the values don't change depending on the
diff --git a/lib/common.go b/lib/common.go
index d93f776..20c173c 100644
--- a/lib/common.go
+++ b/lib/common.go
@@ -10,7 +10,7 @@ import (
 
 const (
 	myname    = "pstop"
-	copyright = "Copyright (C) 2014 Simon J Mudd <sjmudd@pobox.com>"
+	copyright = "Copyright (C) 2014-2015 Simon J Mudd <sjmudd@pobox.com>"
 	i_1024_2  = 1024 * 1024
 	i_1024_3  = 1024 * 1024 * 1024
 	i_1024_4  = 1024 * 1024 * 1024 * 1024
diff --git a/version/version.go b/version/version.go
index 16782b6..95fe521 100644
--- a/version/version.go
+++ b/version/version.go
@@ -2,7 +2,7 @@
 package version
 
 const (
-	version = "0.3.3"
+	version = "0.3.4"
 )
 
 // return the current application version
-- 
2.7.4