Versioning about keydb

[JohnSully]

Hi Floren.

The short answer is I backed myself into a corner by starting at 0.9. The r releases are for the case where a major bug is fixed but otherwise there were no changes to functionality.

Once we hit 1.0 the third digit will cover this case. The second digit will be for new features with no compatibility issues. And the major digit will be for major new features that are now stable.

Once advanced replication is stable we'll go to 1.0 and a more sane format.

[JohnSully]

Also just an FYI I'm a few days away from releasing 0.9.5.

Most people try us through docker not compiling so it encourages frequent releases on my part.

[fmunteanu]

Thanks for taking the time to post the details, I'm going to open a new ticket with the issues I have compiling KeyDB with MALLOC=memkind enabled.

[JohnSully]

I just tested memkind and it works for me (famous last words).

Make sure you have all the dependencies:
sudo apt install build-essential nasm autotools-dev autoconf libjemalloc-dev tcl tcl-dev uuid-dev

The main one being autotools-dev and autoconf. The errors with memkind get buried and its quite hard to see the actual problem, but its almost always missing autotools and autoconf.

[fmunteanu]

@JohnSully this is why is bad practice to use this type of versioning:

Start: rpmbuild -bs
error: line 5: Illegal char '-' in: Version:                0.9.4-r2

[JohnSully]

Will it suffice if I do 0.9.4.2 for now?

[fmunteanu]

Not a problem @JohnSully , I'll wait for 0.9.5 😄

[JohnSully]

0.9.5 is released!