summaryrefslogtreecommitdiff
path: root/00-RELEASENOTES
diff options
context:
space:
mode:
authorantirez <antirez@gmail.com>2012-02-07 15:08:38 +0100
committerantirez <antirez@gmail.com>2012-02-07 15:08:38 +0100
commit01e95705f8d4b0d21cf892748eaf153f16fbf947 (patch)
tree736ca43d2a85eb13412f245130835e8e0ab1824f /00-RELEASENOTES
parentc2513ecb9877d9976da31bc11f84e1dab68777b5 (diff)
downloadredis-01e95705f8d4b0d21cf892748eaf153f16fbf947.tar.gz
Fixes to 2.6 release notes file
Diffstat (limited to '00-RELEASENOTES')
-rw-r--r--00-RELEASENOTES20
1 files changed, 9 insertions, 11 deletions
diff --git a/00-RELEASENOTES b/00-RELEASENOTES
index dd87cb18a..49221f2c0 100644
--- a/00-RELEASENOTES
+++ b/00-RELEASENOTES
@@ -3,18 +3,15 @@ Redis 2.6 release notes
Migrating from 2.4 to 2.6
=========================
-Redis 2.4 is mostly a strict subset of 2.6.
-The only thing you should be aware is that you can't use .rdb and AOF files
-generated with 2.4 into a 2.2 instance.
+Redis 2.4 is mostly a strict subset of 2.6. However there are a few things
+that you should be aware of:
-2.4 slaves can be attached to 2.2 masters, but not the contrary, and only for
-the time needed to perform the version upgrade.
+* You can't use .rdb and AOF files generated with 2.6 into a 2.4 instance.
+* 2.4 slaves can be attached to 2.6 masters, but not the contrary, and only
+ for the time needed to perform the version upgrade.
-From the point of view of the API Redis 2.4 only adds new commands
-(other commands now accepts a variable number of arguments) so you don't need
-to modify your program in order to use Redis 2.4.
-
-However there are a few semantical differences that you should be aware of:
+There are also a few API differences, that are unlikely to cause problems,
+but it is better to keep them in mind:
* SORT now will refuse to sort in numerical mode elements that can't be parsed
as numbers.
@@ -22,7 +19,8 @@ However there are a few semantical differences that you should be aware of:
break code that was not conceived exploting the previous resolution error
in some way.)
* INFO output is a bit different now, and contains empty lines and comments
- starting with '#'.
+ starting with '#'. All the major clients should be already fixed to work
+ with the new INFO format.
---------
CHANGELOG