Live data from Hacker News

Redis 2.8.7 is out

groups.google.com

11–20 of 45 posts

Re: Redis 2.8.7 is out

#12
post #4
post #3

Oh, I didn't expected to see a patch release posted here. As I wrote in the announce this patch release is a bit special as it adds a few new features so at least there is something to explore. Btw ask me anything about this release if something is not clear, I'll try to reply at my best.

Just want to say, Thank You for Redis.

+1. I just started learning and using it a few weeks ago; it's been a lot of fun.

Re: Redis 2.8.7 is out

#15
post #10
post #2

You can get it here: http://download.redis.io/releases/redis-2.8.7.tar.gz

Any reason what that isn't served over SSL?

We have digests here: https://github.com/antirez/redis-hashes.

EDIT: sorry replied with a mobile device. Basically we store digests there at Github while the tarballs are in a different server running at Linode. The idea is that is unlikely that an attacker can gain access to both the Github repository and the server where the tarballs are stored.

However security conscious users need to download the tar.gz and verify the digest manually or via a script (the format is computer parseable).

Re: Redis 2.8.7 is out

#16
post #3

Oh, I didn't expected to see a patch release posted here. As I wrote in the announce this patch release is a bit special as it adds a few new features so at least there is something to explore. Btw ask me anything about this release if something is not clear, I'll try to reply at my best.

Thank you so so much for being in this world and creating Redis, it is wonderful!

Re: Redis 2.8.7 is out

#17
post #3

Oh, I didn't expected to see a patch release posted here. As I wrote in the announce this patch release is a bit special as it adds a few new features so at least there is something to explore. Btw ask me anything about this release if something is not clear, I'll try to reply at my best.

Since I switched to Redis, I had massive drop in resource requirements, saving me a lot of money. Thank you very much.

The keyspace notifications are great but I use NodeJS at the moment to listen to the events. When will it be possible to run Lua to remove the current point of failure? On the topics page, it says "In the future". Are we looking at years or months?

Re: Redis 2.8.7 is out

#18
post #3

Oh, I didn't expected to see a patch release posted here. As I wrote in the announce this patch release is a bit special as it adds a few new features so at least there is something to explore. Btw ask me anything about this release if something is not clear, I'll try to reply at my best.

The most mundane question in the world - why not 2.9? New feature usually means minor version increment, yes?

Re: Redis 2.8.7 is out

#19
post #3

Oh, I didn't expected to see a patch release posted here. As I wrote in the announce this patch release is a bit special as it adds a few new features so at least there is something to explore. Btw ask me anything about this release if something is not clear, I'll try to reply at my best.

The most mundane question in the world - why not 2.9? New feature usually means minor version increment, yes?

In order to simplify the development process I've this strange "rule" that new things are admissible in the stable branch patch releases as long as they are very very unlikely to interfere with all the rest.

For example in this case, a testing environment and the other Sentinel changes actually improve reliability. From the point of view of BITPOS, it is a new command that if not used should not modify the behaviour/stability of the rest of the system in any way.

However compare this process with creating a new release. With 2.8.7 I just need to write a changelog, tag the release on Github, and update a few numbers in the web site. With a release the process is very different, we have a number of release candidates before switching to stable and so forth.

Re: Redis 2.8.7 is out

#20
post #3

Oh, I didn't expected to see a patch release posted here. As I wrote in the announce this patch release is a bit special as it adds a few new features so at least there is something to explore. Btw ask me anything about this release if something is not clear, I'll try to reply at my best.

Since I switched to Redis, I had massive drop in resource requirements, saving me a lot of money. Thank you very much. The keyspace notifications are great but I use NodeJS at the moment to listen to the events. When will it be possible to run Lua to remove the current point of failure? On the topics page, it says "In the future". Are we looking at years or months?

Awesome that you improved your stack with Redis, thanks for sharing. I'm not sure about what exact feature you are referring to, please could you describe it? Thanks.
Post reply on HN