From 16c5467d16e37694546762d03439ea7d44b3690b Mon Sep 17 00:00:00 2001
From: leventov <leventov@ya.ru>
Date: Wed, 23 Mar 2016 20:43:22 +0700
Subject: [PATCH] Update chronicle-values dependency to released version,
 prepare for Chronicle Map release

---
 README.md | 2 ++
 pom.xml   | 4 ++--
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 74f22b0c4..6988e3026 100644
--- a/README.md
+++ b/README.md
@@ -69,6 +69,8 @@ queries*.
  Chronicle Map project, there are projects *on top* of Chronicle Map which address these questions,
  e. g. [Chronicle Enterprise](http://chronicle.software/products/chronicle-enterprise/).
 
+**Project status: ready for production.**
+
 **What is the Chronicle Map's data structure?** In one sentence and simplified, a Chronicle Map
 data store is a big chunk of shared memory (optionally mapped to disk), split into independent
 segments, each segment has an independent memory allocation for storing the entries, a hash table
diff --git a/pom.xml b/pom.xml
index c60abb41e..8b5696a98 100755
--- a/pom.xml
+++ b/pom.xml
@@ -26,7 +26,7 @@
 
     <modelVersion>4.0.0</modelVersion>
     <artifactId>chronicle-map</artifactId>
-    <version>3.8.0-rc-SNAPSHOT</version>
+    <version>3.8.0-SNAPSHOT</version>
     <name>OpenHFT/Chronicle-Map</name>
     <description>Chronicle-Map</description>
     <packaging>bundle</packaging>
@@ -63,7 +63,7 @@
         <dependency>
             <groupId>net.openhft</groupId>
             <artifactId>chronicle-values</artifactId>
-            <version>1.0.7-alpha-SNAPSHOT</version>
+            <version>1.0.7-alpha</version>
         </dependency>
 
         <dependency>