All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-announce@lists.linbit.com, drbd-user@lists.linbit.com
Subject: [DRBD-announce] drbd-9.0.0pre7.tar.gz
Date: Sun, 22 Dec 2013 22:26:03 +0100	[thread overview]
Message-ID: <1446368.FGFGzKY3zx@quad> (raw)

Hi,

Since the last pre-release DRBD9 got a very long way. Since the last
pre-release we developed an automated test suite for DRBD9. This new
test suite turned out to be a reliable source of DRBD9 bugs.
We have not yet emptied this pool of known bugs, therefore we did
not feel the need for a new pre-release.
In the same time period we got a new member in our development team,
working dedicated on the upcoming "drbdmanage" component. This effort
as well fills our DRBD9 bug queue.

Besides all this good news about hard and successful testing of the
code I really need to point out:

 It became a _lot_ better! Did DRBD9 crashed or behaved strange the 
 last time you had a look at it? Please try it again!

Please share the bugs/issues you find with us (via one of the
mailing lists)!

All the best and marry X-mas!


9.0.0pre7 (api:genl1/proto:86-110)
--------
 * Merge up and beyond 8.4.4
 * Do not crash if DRBD runs out of available bitmap slots
 * Fix reference counting (A few bugs in this area caused crashed
   when/after unloading the module)
 * Fix crashes on PAE/highmem
 * Many fixes to the two phase commit protocol (used for cluster
   wide state changes)
 * Lots of minor fixes

http://oss.linbit.com/drbd/9.0/drbd-9.0.0pre7.tar.gz
http://git.drbd.org/gitweb.cgi?p=drbd-9.0.git;a=tag;h=drbd-9.0.0pre7



                 reply	other threads:[~2013-12-22 21:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1446368.FGFGzKY3zx@quad \
    --to=philipp.reisner@linbit.com \
    --cc=drbd-announce@lists.linbit.com \
    --cc=drbd-user@lists.linbit.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.