-----BEGIN PGP SIGNED MESSAGE-----
first of all I am very happy to announce that Digimer is going to be
our new release manager.
Digimer has been contributing to the cluster project in many many
different ways, very active and helpful in the community, with a
strong dedication to write documentation, testing and endless other
So I finally decided to pop the question and Digimer happily accepted
to take over the responsibility for cluster release management.
The transition is going to be smooth and done over time, please be
gentle as one of the worst nightmare in preparing the very first
release, and generally 99% of the time doesn't even build
- From a stricter technical/versioning side of the story:
- - digimer and I are going to release 3.1.8 soon'ish
- - after that I will lockdown STABLE31 branch temporary and open
We have several dozens commits in the pipe with all kind of bug fixes,
coming from static code analysis. Most of those changes are hard to
test in isolation. Plan is to push those changes in "chunks" into
STABLE32 branch and do simple test releases (3.1.9x), to make it
easier to test. It will be very useful for people to report bugs ASAP.
NOTE TO PACKAGERS: shipping of 3.1.9x is strongly discouraged. Use
your temporary archive/private ppa or secret repositories. Wait for
3.2.x series before uploading to any unstable/stable distribution. You
have been warned.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----