summaryrefslogtreecommitdiff
path: root/00-RELEASENOTES
diff options
context:
space:
mode:
authorantirez <antirez@gmail.com>2012-02-05 11:08:01 +0100
committerantirez <antirez@gmail.com>2012-02-05 11:08:01 +0100
commitc2513ecb9877d9976da31bc11f84e1dab68777b5 (patch)
treee837a94c4bdbc2ee5d80b7adec295ba760cf40b9 /00-RELEASENOTES
parent3508899944aa0797cf52563493b4bc295b0ec2fd (diff)
downloadredis-c2513ecb9877d9976da31bc11f84e1dab68777b5.tar.gz
A first (work in progress) release notes for 2.6
Diffstat (limited to '00-RELEASENOTES')
-rw-r--r--00-RELEASENOTES81
1 files changed, 81 insertions, 0 deletions
diff --git a/00-RELEASENOTES b/00-RELEASENOTES
new file mode 100644
index 000000000..dd87cb18a
--- /dev/null
+++ b/00-RELEASENOTES
@@ -0,0 +1,81 @@
+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.
+
+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.
+
+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:
+
+* SORT now will refuse to sort in numerical mode elements that can't be parsed
+ as numbers.
+* EXPIREs now all have millisecond resolution (but this is very unlikely to
+ 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 '#'.
+
+---------
+CHANGELOG
+---------
+
+What's new in Redis 2.6.0
+=========================
+
+UPGRADE URGENCY: We suggest new users to start with 2.6.0, and old users to
+ upgrade after some testing of the application with the new
+ Redis version.
+
+* Server side Lua scripting, see http://redis.io/commands/eval
+* Virtual Memory removed (was deprecated in 2.4)
+* Hardcoded limits about max number of clients removed.
+* AOF low level semantics is generally more sane, and especially when used
+ in slaves.
+* Milliseconds resolution expires, also added new commands with milliseconds
+ precision (PEXPIRE, PTTL, ...).
+* Clinets max output buffer soft and hard limits. You can specifiy different
+ limits for different classes of clients (normal,pubsub,slave).
+* AOF is now able to rewrite aggregate data types using variadic commands,
+ often producing an AOF that is faster to save, load, and is smaller in size.
+* Every redis.conf directive is now accepted as a command line option for the
+ redis-server binary, with the same name and number of arguments.
+* Hash table seed randomization for protection against collisions attacks.
+* Performances improved when writing large objects to Redis.
+* Significant parts of the core refactored or rewritten. New internal APIs
+ and core changes allowed to develop Redis Cluster on top of the new code,
+ however for 2.6 all the cluster code was removed, and will be released with
+ Redis 3.0 when it is more complete and stable.
+* Redis ASCII art logo added at startup.
+* Crash report on memory violation or failed asserts improved significantly
+ to make debugging of hard to catch bugs simpler.
+* redis-benchmark improvements: ability to run selected tests,
+ CSV output, faster, better help.
+* redis-cli improvements: --eval for comfortable development of Lua scripts.
+* SHUTDOWN now supports two optional arguments: "SAVE" and "NOSAVE".
+* INFO output split into sections, the command is now able to just show
+ pecific sections.
+* New statistics about how many time a command was called, and how much
+ execution time it used (INFO commandstats).
+* More predictable SORT behavior in edge cases.
+* INCRBYFLOAT and HINCRBYFLOAT commands.
+
+--------------------------------------------------------------------------------
+
+Credits: Where not specified the implementation and design are done by
+Salvatore Sanfilippo and Pieter Noordhuis. Thanks to VMware for making all
+this possible. Also many thanks to all the other contributors and the amazing
+community we have.
+
+See commit messages for more credits.
+
+Cheers,
+Salvatore