diff --git a/src/java/voldemort/store/bdb/dataconversion/READMEFIRST b/bin/PREUPGRADE_FOR_1_1_X_README
similarity index 92%
rename from src/java/voldemort/store/bdb/dataconversion/READMEFIRST
rename to bin/PREUPGRADE_FOR_1_1_X_README
index d31ae6ccd8..2cde462b4e 100644
--- a/src/java/voldemort/store/bdb/dataconversion/READMEFIRST
+++ b/bin/PREUPGRADE_FOR_1_1_X_README
@@ -14,7 +14,7 @@ This section describes the data formats themselves.
 
 1) Base Format (Base)
 --------------------- 
-This is the format used by Voldemort up until 1.x, relying on BDB JE for 
+This is the format used by Voldemort up until 1.1.x, relying on BDB JE for 
 duplicate handling
 
 Disadvantages:
@@ -27,7 +27,7 @@ Disadvantages:
 
 2) New duplicate format (NewDup)
 -------------------------------- 
-This format is supported from release 1.x, where Voldemort storage layer 
+This format is supported from release 1.1.x, where Voldemort storage layer 
 handles duplicates and BDB JE version is bumped up to JE 4.1.17 
 
 Advantages:
@@ -41,11 +41,11 @@ Advantages:
    of an additional delete()
 -- General speed up due to elimination of duplicates
 
-This format is the minimum requirement to be able to upgrade to 1.x & higher
+This format is the minimum requirement to be able to upgrade to 1.1.x & higher
 
 3) Partition Scan format (PidScan)
 ----------------------------------
-This is a super set of 'NewDup' format, supported 1.x upwards. In addition to
+This is a super set of 'NewDup' format, supported 1.1.x upwards. In addition to
 eliminating duplicates and upgrading to JE 4.1.17, it adds a 2 byte prefix  
 representing the partition id to each key. 
 
@@ -60,7 +60,7 @@ Note : We have not seen the extra 2 bytes cause any overhead to online
 performance 
 
 IMPORTANT: IT IS REQUIRED TO CONVERT TO EITHER 'NewDup' or 'PidScan' TO RUN 
-VOLDEMORT WITH BDB, STARTING RELEASE 1.x
+VOLDEMORT WITH BDB, STARTING RELEASE 1.1.x
 
 Running the Conversion Utility
 ------------------------------
@@ -88,7 +88,7 @@ $./voldemort-convert-bdb.sh --src   <Required: Path to source bdb environment>
                                     Default:60>
                       --btree-nodemax <Optional: Btree fan out, Default: 512>
                       
-We recommend you run the following to move to release 1.x & up.
+We recommend you run the following to move to release 1.1.x & up.
 
 $./voldemort-convert-bdb.sh --src   /path/to/src/env
                       --dest  /path/to/dest/env 
diff --git a/build.properties b/build.properties
index f5bf1aa2de..a40a432e83 100644
--- a/build.properties
+++ b/build.properties
@@ -39,4 +39,4 @@ tomcat.manager.password=tomcat
 tomcat.context=/voldemort
 
 ## Release
-curr.release=1.0.0
+curr.release=1.1.0
diff --git a/release_notes.txt b/release_notes.txt
index bd77ab6bb9..8aa089d733 100644
--- a/release_notes.txt
+++ b/release_notes.txt
@@ -1,3 +1,22 @@
+Release 1.1.0.on 10/19/2012
+
+Changes made since release 1.1.0
+
+IMPORTANT NOTE : This release has significant changes to the BDB storage layer.
+Users are required to read the bin/PREUPGRADE_FOR_1_1_X_README file
+thoroughly before attempting to upgrade to 1.1.0. The necessary data 
+conversion will be done through bin/voldemort-convert-bdb.sh
+
+* Upgrading to JE 4.1.17
+* New data format that handles conflicting updates in Voldemort more
+  efficiently
+* Move data off heap and only use it for Index
+* When scanning, evict whatever you bring in right away.
+* Partition based scan api to dramatically speed up rebalancing & restore
+  using Partition aware scans (you exactly scan whatever you want to fetch)
+* Flexible knobs to control scheduling of DataCleanupJob
+
+
 Release 1.0.0 on 10/17/2012
 
 NOTE: The large version number jump from 0.96 to 1.0.0 is to