X-Git-Url: https://git.saurik.com/redis.git/blobdiff_plain/1a3e9d951be14fecf29cb7ad3d5f068e151b66f1..05e06e154332cf107d30092dddb94b6b35967ce5:/00-RELEASENOTES diff --git a/00-RELEASENOTES b/00-RELEASENOTES index 031a433e..12f1e3d1 100644 --- a/00-RELEASENOTES +++ b/00-RELEASENOTES @@ -10,10 +10,69 @@ Upgrade urgency levels: 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 some part of users. Upgrade! +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. -------------------------------------------------------------------------------- +---[ Redis 2.5.13 (2.6 Release Candidate 7) ] + +UPGRADE URGENCY: HIGH + +* [BUGFIX] Theoretical bug in ziplist fixed. +* [BUGFIX] Better out of memory handling (Log produced in log file). +* [BUGFIX] Incrementally flush RDB file on slave side while performing the + first synchronization with the master. This makes Redis less + blocking in environments where disk I/O is slow. +* [BUGFIX] Don't crash with Lua's redis.call() without arguments. +* [BUGFIX] Don't crash after a big number of Lua calls on 32 bit systems + because of a failed assertion. +* [BUGFIX] Fix SORT behaviour when called from scripting. +* [BUGFIX] Adjust slave PING period accordingly to REDIS_HZ define. +* [BUGFIX] BITCOUNT: fix crash on overflowing arguments. +* [BUGFIX] Return an error when SELECT argument is not an integer. +* [BUGFIX] Blocking operations on lists were completely reimplemented for + correctness. Now blocking list ops and pushes originated from + Lua scripts will play well together and will be replicated + and transmitted to the AOF correctly. +* [IMPROVED] Send async PING before starting replication to avoid blocking if + master allows us to connect but it is actually not able to reply. +* [IMPROVED] Support slave-priority for Redis Sentinel. +* [IMPROVED] Hiredis library updated. + +---[ Redis 2.5.12 (2.6 Release Candidate 6) ] + +UPGRADE URGENCY: MODERATE. + +* [BUGFIX] Fixed a timing attack on AUTH (Issue #560). +* [BUGFIX] Don't assume that "char" is signed. +* [BUGFIX] Check that we have connection before enabling pipe mode. +* [BUGFIX] Use the optimized version of the function to convert a double to + its string representation. Compilation was disabled because of + a typo in the #if statement. +* [IMPROVED} REPLCONF internal command introduced, now INFO shows slaves with + correct port numbers. This makes 2.5.12 Redis Sentinel compatible. +* [IMPROVED] Truncate short write from the AOF for a cleaner restart. On short + writes (for instance out of space) Redis will now try to remove + the half-written data so that the next restart will work without + the need for the "redis-check-aof" utility. +* [IMPROVED] New in INFO: aof_last_bgrewrite_status +* [IMPROVED] Allow Pub/Sub in contexts where other commands are blocked. +* [BUGFIX] mark fd as writable when EPOLLERR or EPOLLHUP is returned by + epoll_wait. + +---[ Redis 2.5.11 (2.6 Release Candidate 5) ] + +UPGRADE URGENCY: HIGH. + +* [BUGFIX] Fixed Hash corruption when loading an RDB file generated by + previous versions of Redis that encoded hashes using + a different ziplist encoding format for small integers. + All the fileds that are integers in the range 0-255 may not + be recognized, or duplicated un updates, causing a crash + when the ziplist is converted to a real hash. (Issue #547). +* [BUGFIX] Fixed the count of memory used by output buffers in the + setDeferredMultiBulkLength() function. + ---[ Redis 2.5.10 (2.6 Release Candidate 4) ] UPGRADE URGENCY: HIGH. @@ -123,7 +182,7 @@ Redis 2.4 is mostly a strict subset of 2.6. However there are a few things that you should be aware of: * 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 +* 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. There are also a few API differences, that are unlikely to cause problems,