Distributed Replicated Block Device (DRBD) announcements
 help / color / mirror / Atom feed
From: Johannes Thoma <johannes.thoma@linbit.com>
To: drbd-announce@lists.linbit.com
Subject: WinDRBD 1.2.3 released
Date: Wed, 24 Sep 2025 16:33:37 +0200	[thread overview]
Message-ID: <71ebe7e8-224b-4b06-9872-b2dcadf8cb63@linbit.com> (raw)

Dear WinDRBD community,

We just released WinDRBD 1.2.3. Besides the funny version number
(does anybody remember Lotus 1-2-3?) it comes with 2 stability
fixes in conjunction with disconnecting resources, one of them
was actually a DRBD bug and is merged upstream.

This version is based on the newest DRBD 9.2.15 release which was
released just 2 days ago and hence comes with all the improvements of
DRBD 9.2.15.

It also comes with clang as a build toolchain support which allows us
to use the Microsoft WinDbg debugger, since clang is able to output
Microsoft's PDB debugging symbols files. This eases development a lot.

It is not super urgent to upgrade to this version since most of the
defects fixed therein are corner cases but if you have a maintenance
window it is recommended that you upgrade WinDRBD as well.

Best regards,

- Johannes

                 reply	other threads:[~2025-09-24 14:33 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=71ebe7e8-224b-4b06-9872-b2dcadf8cb63@linbit.com \
    --to=johannes.thoma@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox