From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] fence-agents-3.1.5 stable release
Date: Fri, 08 Jul 2011 14:28:09 +0200 [thread overview]
Message-ID: <4E16F7D9.9040903@redhat.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Welcome to the fence-agents 3.1.5 release.
This release includes a few minor bug fixes and support for more devices
(Eaton Switched ePDU).
The new source tarball can be downloaded here:
https://fedorahosted.org/releases/f/e/fence-agents/fence-agents-3.1.5.tar.xz
To report bugs or issues:
https://bugzilla.redhat.com/
Would you like to meet the cluster team or members of its community?
Join us on IRC (irc.freenode.net #linux-cluster) and share your
experience with other sysadministrators or power users.
Thanks/congratulations to all people that contributed to achieve this
great milestone.
Happy clustering,
Fabio
Under the hood (from 3.1.4):
Arnaud Quette (1):
eaton_snmp: add support for Eaton Switched ePDU
Fabio M. Di Nitto (3):
relaxng: ship bits required to build the schema at runtime
relaxng: drop <grammar> definition
relaxng: drop static agents definitions
Lon Hohberger (1):
Make fence_ack_manual 'usage' more accessible
Marek 'marx' Grac (3):
fence_drac5: Fix support for Dell DRAC CMC
fence_bladecenter: Reboot operation did not work correctly with
- --missing-
fence_drac5: Incorrect output of 'list' operation on Drac 5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBCAAGBQJOFvfXAAoJEFA6oBJjVJ+OjbsP/1pP6I2W86x++n+OJpOUvfNK
9ZXFBMvz3hphqHcYkACgoKE5qmQDYgCdH5EmJXrO4iQ0fCZ16/vyH2USqG3CqO7h
3VozL78IHjM8YDlssoWjD/vbzK5w6KbaC4Qpy2vcW73ARi1Ot0vsJN9InexyKorl
XAT4MIBqdJNwSfI2wGT9pe1duoY0AqNrz+UlRssXjYgaxlxq/5LtVmbRnRpbypqO
yBLtspTK+fSy0ofD2hxsOpTHDSgmMaj8REeN49iP924JbKbGE0FBl5yHh4Kd7UGI
6Q5gdbm7PetZAz9jubbJdH2yKRV5C0btzlvH7/LJsL4AK8qjA49cz7erygRU0sRv
1HOKFJ+xIWiNvp/I5AYhjIjMc0r1Eafrmpg7FgyhG9bNM6avmh7KiTSAxXfwOjRK
H22uakA/cxwOGWMMwLfRsSqwh5H9QTDRrXbF2xMHuenq/qDVvgHxveFoLqWQSdGd
HFsbcjWtfcPNer/+Fawk/7FoDkh2K0+EuhaPJdNplk+NkyTjw+EE67z6tdnislWB
0Ocx8YwX3ID7QjwySxPCNoayuUKUjDJiOgugEiHf4PrbGoqczQHug6O49IUwb2ZR
oT2DwpJnMptQluh1f5Xkw7OLB+tVA8elbnDjqzejB/5aj4LGZy2r/3OrQkOGfdnK
Stv3UdSiSk0mdv9SPF6F
=omcd
-----END PGP SIGNATURE-----
reply other threads:[~2011-07-08 12:28 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=4E16F7D9.9040903@redhat.com \
--to=fdinitto@redhat.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;
as well as URLs for NNTP newsgroup(s).