summaryrefslogtreecommitdiff
path: root/00-RELEASENOTES
diff options
context:
space:
mode:
authorantirez <antirez@gmail.com>2014-02-10 15:36:02 +0100
committerantirez <antirez@gmail.com>2014-02-10 15:36:02 +0100
commitff6a75a0c1afc2d3f7acc7ff098d0fd27870b738 (patch)
tree8592443b93f03ac72e48a591f676ffd722bcb2d1 /00-RELEASENOTES
parentb1c3c6e5181e5ff4200155036bea48c935566054 (diff)
downloadredis-ff6a75a0c1afc2d3f7acc7ff098d0fd27870b738.tar.gz
3.0 release notes added.
Diffstat (limited to '00-RELEASENOTES')
-rw-r--r--00-RELEASENOTES96
1 files changed, 29 insertions, 67 deletions
diff --git a/00-RELEASENOTES b/00-RELEASENOTES
index 36317ca35..8bdd2cf2f 100644
--- a/00-RELEASENOTES
+++ b/00-RELEASENOTES
@@ -1,83 +1,45 @@
-Redis 2.6 release notes
+Redis 3.0 release notes
+=======================
-Migrating from 2.4 to 2.6
-=========================
-
-Redis 2.4 is mostly a strict subset of 2.6. However there are a few things
-that you should be aware of:
+WARNING: Redis 3.0 is currently a BETA not suitable for production environments.
-* You can't use .rdb and AOF files generated with 2.6 into a 2.4 instance.
-* 2.6 slaves can be attached to 2.4 masters, but not the contrary, and only
- for the time needed to perform the version upgrade.
+--------------------------------------------------------------------------------
+Upgrade urgency levels:
-There are also a few API differences, that are unlikely to cause problems,
-but it is better to keep them in mind:
+LOW: No need to upgrade unless there are new features you want to use.
+MODERATE: Program an upgrade of the server, but it's not urgent.
+HIGH: There is a critical bug that may affect a subset of users. Upgrade!
+CRITICAL: There is a critical bug affecting MOST USERS. Upgrade ASAP.
+--------------------------------------------------------------------------------
-* 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 '#'. All the major clients should be already fixed to work
- with the new INFO format.
+--[ Redis 3.0.0 Beta 1 (version 2.9.50) ] Release date: ...
-Also the following redis.conf and CONFIG GET / SET parameters changed name:
+This is the first beta of Redis 3.0.0 (official version is 2.8.50).
- * hash-max-zipmap-entries, now replaced by hash-max-ziplist-entries
- * hash-max-zipmap-value, now replaced by hash-max-ziplist-value
- * glueoutputbuf was now completely removed as it does not make sense
+The following is a list of improvements in Redis 3.0, compared to Redis 2.8.
----------
-CHANGELOG
----------
+* [NEW] Redis Cluster: a distributed implementation of a subset of Redis.
+* [NEW] New "embedded string" object encoding resulting in less cache
+ misses. Big speed gain under certain work loads.
+* [NEW] WAIT command to block waiting for a write to be transmitted to
+ the specified number of slaves.
+* [NEW] MIGRATE connection caching. Much faster keys migraitons.
+* [NEW] MIGARTE new options COPY and REPLACE.
+* [NEW] CLIENT PAUSE command: stop processing client requests for a
+ specified amount of time.
-What's new in Redis 2.6.0
+Migrating from 2.8 to 3.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, ...).
-* Clients 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.
+Redis 3.0 is mostly a strict subset of 2.8, you should not have any problem
+upgrading your application from 2.8 to 3.0.
--------------------------------------------------------------------------------
-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.
+Credits: Where not specified the implementation and design is done by
+Salvatore Sanfilippo. Thanks to Pivotal 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.