Redis 2.6 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:
-
-* 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.
-
-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.
-* 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.
-* Slaves are only read-only by default (but you can change this easily
- setting the "slave-read-only" configuration option to "no" editing your
- redis.conf or using CONFIG SET.
+** IMPORTANT ** Check the 'Migrating from 2.4 to 2.6' section at the end of
+ this file for information about what changed between 2.4 and
+ 2.6 and how this may affect your application.
-Also the following redis.conf and CONFIG GET / SET parameters changed name:
+--------------------------------------------------------------------------------
+Upgrade urgency levels:
- * hash-max-zipmap-entries, now replaced by hash-max-ziplist-entries
- * hash-max-zipmap-value, now replaced by hash-max-ziplist-value
- * glueoutputbuf option was now completely removed (was deprecated)
+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!
+CRITICAL: There is a critical bug affecting MOST USERS. Upgrade ASAP.
+--------------------------------------------------------------------------------
----------
-CHANGELOG
----------
+---[ 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.
+
+* [BUGFIX] Allow PREFIX to be overwritten on "make install".
+* [BUGFIX] Run the test with just one client if the computer is slow.
+* [BUGFIX] Event port support in our event driven libray.
+* [BUGFIX] Jemalloc updated to 3.0.0. This fixes a possibly AOF rewrite issue.
+ See https://github.com/antirez/redis/issues/504 for info.
+* [BUGFIX] Fixed issue #516: ZINTERSTORE / ZUNIONSTORE with mixed sets/zsets.
+* [BUGFIX] Set fd to writable when poll(2) detects POLLERR or POLLHUP event.
+* [BUGFIX] Fixed RESTORE hash failure (Issue #532).
+* [IMPROVED] Allow an AOF rewrite buffer > 2GB (Related to issue #504).
+* [IMPROVED] Server cron function frequency is now configurable (REDIS_HZ).
+* [IMPROVED] Better, less blocking expired keys collection algorithm.
+* [FEATURE] New commands: BITOP and BITCOUNT.
+* [FEATURE] redis-cli --pipe for mass import.
What's new in Redis 2.5.9 (aka 2.6 Release Candidate 3)
=======================================================
* [BUGFIX] Fix for issue #500 (https://github.com/antirez/redis/pull/500).
Redis 2.6-RC1 and RC2 may corrupt ziplist-encoded sorted sets
produced by Redis 2.4.x.
+* [BUGFIX] Fixed several bugs in init.d script.
+* [BUGFIX] syncio.c functions modified for speed and correctness. On osx
+ (and possibly other BSD-based systems) the slave would block on
+ replication to send the SYNC command when the master was not
+ available. This is fixed now, but was not affecting Linux installs.
+* Now when slave-serve-stale-data is set to yes and the master is down, instead
+ of reporting a generic error Redis replies with -MASTERDOWN.
What's new in Redis 2.5.8 (aka 2.6 Release Candidate 2)
=======================================================
* Better memory usage for "small" lists, ziplists and hashes when fields or
values contain small integers.
* Read only slaves.
+* New bit opeations: BITCOUNT and BITOP commands.
* Clients max output buffer soft and hard limits. You can specifiy different
limits for different classes of clients (normal,pubsub,slave).
+* More incremental (less blocking) expired keys collection algorithm, in
+ practical terms this means that Redis is more responsive when a very
+ big number of keys expire about at the same time.
* 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
* Better support for big endian and *BSD systems.
* Build system improved.
+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:
+
+* 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.
+
+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.
+* 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.
+* Slaves are only read-only by default (but you can change this easily
+ setting the "slave-read-only" configuration option to "no" editing your
+ redis.conf or using CONFIG SET.
+
+The following INFO fields were renamed for consistency:
+
+ changes_since_last_save -> rdb_changes_since_last_save
+ bgsave_in_progress -> rdb_bgsave_in_progress
+ last_save_time -> rdb_last_save_time
+ last_bgsave_status -> rdb_last_bgsave_status
+ bgrewriteaof_in_progress -> aof_rewrite_in_progress
+ bgrewriteaof_scheduled -> aof_rewrite_scheduled
+
+The following redis.conf and CONFIG GET / SET parameters changed:
+
+ * hash-max-zipmap-entries, now replaced by hash-max-ziplist-entries
+ * hash-max-zipmap-value, now replaced by hash-max-ziplist-value
+ * glueoutputbuf option was now completely removed (was deprecated)
+
--------------------------------------------------------------------------------
Credits: Where not specified the implementation and design are done by