Skip to content

Commit e2ee20d

Browse files
antirezjmedrano
authored andcommitted
Latest doc changes for 1.0
Signed-off-by: jmedrano <[email protected]>
1 parent 63e81a7 commit e2ee20d

File tree

2 files changed

+6
-7
lines changed

2 files changed

+6
-7
lines changed

Changelog

+5
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,8 @@
1+
2009-09-03 Redis 1.0.0 release
2+
2009-09-02 Redis version pushed to 1.0
3+
2009-09-02 Ruby client lib updated to the latest git version
4+
2009-09-02 update-scala-client script added
5+
2009-09-02 Scala client added thanks to Alejanro Crosa
16
2009-09-02 QuickStart added
27
2009-09-01 Fixed crash with only space and newline as command (issue 61), thanks to a guy having as nick "fixxxerrr"
38
2009-08-11 TODO list modified

TODO

+1-7
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,4 @@
1-
BEFORE REDIS 1.0.0-rc1
2-
3-
* Cover most of the source code with test-redis.tcl
41
* Expiring algorithm should be adaptive, if there are a lot of keys with an expire set and many of this happen to be already expired it should be, proportionally, more aggressive.
5-
6-
AFTER 1.0 stable release
7-
82
* Add a command to inspect the currently selected DB index
93
* Consistent hashing implemented in all the client libraries having an user base
104
* SORT: Don't copy the list into a vector when BY argument is constant.
@@ -22,7 +16,7 @@ AFTER 1.0 stable release
2216
the elements by 'score', with the actual value being the key. On the other
2317
side the type also takes an hash table with key->score mapping, so that when
2418
there is an update we lookup the current score and can traverse the tree.
25-
* BITMAP type
19+
* BITMAP / BYTEARRAY type?
2620
* LRANGE 4 0 should return the same elements as LRANGE 0 4 but in reverse order (only if we get enough motivated requests about it)
2721
* zmalloc() should avoid to add a private header for archs where there is some other kind of libc-specific way to get the size of a malloced block.
2822

0 commit comments

Comments
 (0)