Prepare for release 0.1.5spice-html5-0.1.5

3 files changed, 10 insertions, 12 deletions

diff --git a/README b/README
index 6e5c5a8..5069209 100644
--- a/README
+++ b/README
@@ -1,10 +1,10 @@
-Prototype Spice Javascript client
+Spice Javascript client
 
-Instructions and status as of June 1, 2012.
+Instructions and status as of September, 2014.
 
 Requirements:
 
-  1.  Modern Firefox or Chrome
+  1.  Modern Firefox or Chrome (IE will work, but badly)
       
   2.  A WebSocket proxy
 
@@ -19,10 +19,6 @@ Requirements:
       a Fedora image, a Vista image, and with Xspice.  
       Vista was pretty bad; I recommend either Linux or Xspice.
 
-      ** Xspice has a processing issue; see this email:
-         http://lists.freedesktop.org/archives/spice-devel/2012-May/009020.html
-
-
 Optional:
   1.  A web server
 
@@ -46,6 +42,3 @@ Status:
 
   The TODO file should be a fairly comprehensive list of tasks
   required to make this client more fully functional.
-
-  As of June 1, 2012, this client is a nifty proof of concept,
-  but a long way from being a useful production tool.
diff --git a/TODO b/TODO
index 2ef25be..cf92c9c 100644
--- a/TODO
+++ b/TODO
@@ -45,7 +45,7 @@ Big Tasks:
   . Profile the whole mess
     - Initial profiling suggests image decompression is the big hog
 
-  . Implement agent support
+  . Improve agent support
 
   . Build a test suite for measuring performance
     - Latency, bandwidth, packet loss
diff --git a/spice-html5.spec.in b/spice-html5.spec.in
index 5eed4d3..f69e051 100644
--- a/spice-html5.spec.in
+++ b/spice-html5.spec.in
@@ -1,6 +1,6 @@
 Name:           spice-html5
 Version:        VERSION
-Release:        2%{?dist}
+Release:        1%{?dist}
 Summary:        Pure Javascript SPICE client
 
 License:        LGPLv3
@@ -30,6 +30,11 @@ file for Apache, but should work with any web server.
 
 
 %changelog
+* Thu Sep 25 2014 Jeremy White <jwhite@codeweavers.com> 0.1.5-1
+- If an agent is attached, enable dynamic resizing of the guest screen.
+- Add support for audio streams using the Opus encoding.
+- Vladik Romanovsky: Use wss scheme when accessing with https protocol
+
 * Thu Sep 19 2013 Jeremy White <jwhite@codeweavers.com> 0.1.4-1
 - Reduce memory leaks
 - Ack every message.