X-Git-Url: https://git.saurik.com/redis.git/blobdiff_plain/0c9cf45270141d9f7bb1124a98fbe8c8d2e1d461..b58f03a0e858bd55f61f8865bfb58bdbb45c232b:/00-RELEASENOTES

diff --git a/00-RELEASENOTES b/00-RELEASENOTES
index 5c76973d..9c0afd37 100644
--- a/00-RELEASENOTES
+++ b/00-RELEASENOTES
@@ -14,6 +14,27 @@ HIGH:     There is a critical bug that may affect some part of users. Upgrade!
 CRITICAL: There is a critical bug affecting MOST USERS. Upgrade ASAP.
 --------------------------------------------------------------------------------
 
+---[ 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.
@@ -136,7 +157,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,