From: NeilBrown <neilb@suse.de>
To: linux RAID <linux-raid@vger.kernel.org>
Subject: Planning a bug-fix release for mdadm: mdadm 3.2.6
Date: Thu, 18 Oct 2012 15:48:07 +1100 [thread overview]
Message-ID: <20121018154807.461ddd29@notabene.brown> (raw)
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
Hi all,
I had hoped to be close to releasing mdadm-3.3 by now but that doesn't look
like it'll happen for a couple of months.
So I'm planning on releasing 3.2.6 which just has bug-fixes on top of 3.2.5
- no new features or possible breakage.
The "mdadm-3.2.x" branch of my git tree (git://neil.brown.name/mdadm)
contains what I have so far. If anyone knows of bugs in current mdadm that
really should be fixed for the next release and aren't in that tree, please
let me know (or even send me a patch).
If nothing happens to change my mind I'll release 3.2.6 seven days from now
(which is Thursday afternoon in my time zone - GMT+11).
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next reply other threads:[~2012-10-18 4:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 4:48 NeilBrown [this message]
2012-10-20 15:28 ` Planning a bug-fix release for mdadm: mdadm 3.2.6 Michael Tokarev
2012-10-20 15:44 ` Michael Tokarev
2012-10-21 22:01 ` NeilBrown
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=20121018154807.461ddd29@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).