what is the ETA on 2.6
Jak Sprats
When do you guys expect to drop 2.6 RC1 and do you have a decent idea
of the features-list?
Also any ETA updates on redis 3.0 would be appreciated.
And the last line of this page: http://redis.io/download says a redis
cluster beta should be ready by the end of year 2011, so that needs an
update before someone complains about it :)
OK, just any time estimates (even guesses) would be helpful
thanks,
jak
Pieter Noordhuis
Currently Salvatore is busy trying to kill bugs before the 2.6 RC, but
other than that it is as good as feature complete. One other thing
that will be included is the changed hash encoding: it will use the
ziplist instead of the zipmap for 2.6, thereby unifying the memory
layout for special types.
After the RC is out and no bugs surface, I guess it'll be declared
stable pretty soon. After that, 3.0 work continues.
Cheers,
Pieter
> --
> You received this message because you are subscribed to the Google Groups "Redis DB" group.
> To post to this group, send email to redi...@googlegroups.com.
> To unsubscribe from this group, send email to redis-db+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/redis-db?hl=en.
>
Salvatore Sanfilippo
in freeze as no new big features are added, with the exception of
small features that have a lot to do with helping bug fixing or
helping sysadmins to do a better work with Redis with less work.
Currently there are a few open issues regarding 2.6, I'm working at
those issues but likely #243 is not going to be fixed before RC1,
simply because after weeks of work we still can't find the root cause,
and the issue only happens to a single user currently.
Because the user experiencing this issue (Dominik) is particularly
cool we are working a lot on this, but because the issue is so rare
and AFAIK is present in Redis since Redis 2.2 (!) I don't see a reason
to have this as a blocking issue.
So long story short, RC1 is going to take a few weeks.
Now... from RC1 to stable it will take a lot probably. I don't know
how much, but I want to be really really sure that everything is ok
before calling it stable. RC1 will be actually stable enough,
remember: stability is not a black/white concept, so we'll try to get
users that need 2.6 features to switch. But we'll call it stable only
after many weeks of testing.
To put it raw: after 2.6 RC1 is released I'll just write tests to
reach full coverage of the source code. When this effort is completed,
2.6 will be called stable, and we'll finally move to Redis 3.0 to
finish the cluster implementation.
Quality, or Death :)
Salvatore
--
Salvatore 'antirez' Sanfilippo
open source developer - VMware
http://invece.org
"We are what we repeatedly do. Excellence, therefore, is not an act,
but a habit." -- Aristotele
Jak Sprats
Quality or Death :)
Beautiful ...
ok, sounds good, thanks much for the reply and for the quality, and
full test coverage for 2.6 will be a ton of work and we all know
writing code to test is no fun, so thanks for that especially
> >> Hi Salvatore & Pieter,
>
> >> When do you guys expect to drop 2.6 RC1 and do you have a decent idea
> >> of the features-list?
>
> >> Also any ETA updates on redis 3.0 would be appreciated.
>
> >> update before someone complains about it :)
>
> >> OK, just any time estimates (even guesses) would be helpful
>
> >> thanks,
> >> jak
>
> >> --
> >> You received this message because you are subscribed to the Google Groups "Redis DB" group.
> >> To post to this group, send email to redi...@googlegroups.com.
> >> To unsubscribe from this group, send email to redis-db+u...@googlegroups.com.
> > --
> > You received this message because you are subscribed to the Google Groups "Redis DB" group.
> > To post to this group, send email to redi...@googlegroups.com.
> > To unsubscribe from this group, send email to redis-db+u...@googlegroups.com.