From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster 3.1.4 release
Date: Fri, 08 Jul 2011 20:57:32 +0200 [thread overview]
Message-ID: <4E17531C.7070305@redhat.com> (raw)
Welcome to the cluster 3.1.4 release.
This release fixes a few bugs and adds a new dynamic relaxng schema
creation.
In order to run this version of cman/cluster, it is strictly required to
have fence-agents at least in version 3.1.5 and resource-agents in
version 3.9.2. Alternatively you have to disable cluster.conf validation
(see ccs_config_validate.8 for information).
The new source tarball can be downloaded here:
https://fedorahosted.org/releases/c/l/cluster/cluster-3.1.4.tar.xz
ChangeLog:
https://fedorahosted.org/releases/c/l/cluster/Changelog-3.1.4
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
reply other threads:[~2011-07-08 18:57 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=4E17531C.7070305@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).