All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Dake <sdake@redhat.com>
To: lvm-devel@redhat.com
Subject: recent stabilization changes to corosync and openais API/ABIs
Date: Sat, 18 Apr 2009 05:53:47 -0000	[thread overview]
Message-ID: <1240034017.5808.135.camel@sdake-laptop> (raw)

Hello,

Some people on these lists may be interested to know what is happening
with Corosync and OpenAIS ABIs as well as our schedules for 1.0.

We are currently planning the following dates for our releases:
Corosync 1.0 - May 15, 2009
OpenAIS 1.0 - June 1, 2009

We have made great progress and the code is seeing good stabilization.
Over the past few weeks, our community team has sanitized the corosync
ABI and APIs.

Specifically the following types of changes were made to corosync:
* A const qualifier was added to any parameter that was a constant
buffer or struct
* Any size parameter was changed from int/unsigned int, to size_t
* Any buffer that was copied into in a calling function added a length
parameter which has a size_t type.
* All of the external headers had these changes applied as well as
coroapi.h.

No significant changes were made to the openais ABI, however, because of
changes to internal apis, we are bumping the so major version requiring
a recompile if you use the SA Forum APIs as dependencies or any corosync
APIs.

We are targeting a new release with these changes to be introduced into
distributions that ship this software in early May.

Regards
-steve




             reply	other threads:[~2009-04-18  5:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-18  5:53 Steven Dake [this message]
2009-04-18  6:04 ` [Pacemaker] recent stabilization changes to corosync and openais API/ABIs Juha Heinanen
2009-04-18  6:25   ` Steven Dake

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=1240034017.5808.135.camel@sdake-laptop \
    --to=sdake@redhat.com \
    --cc=lvm-devel@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 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.