From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] time for STABLE2 branch
Date: Tue, 9 Oct 2007 11:26:34 -0500 [thread overview]
Message-ID: <20071009162634.GA2632@redhat.com> (raw)
In-Reply-To: <20070918214044.GD15032@redhat.com>
On Tue, Sep 18, 2007 at 04:40:45PM -0500, David Teigland wrote:
> I believe the time has arrived for a STABLE2 cluster branch.
>
> CVS HEAD hasn't been usable by most people for quite a while, partly due
> to ugly build requirements and partly due to instability of new code.
> Building HEAD currently requires the unstable version of openais, and a
> gfs2 patch that only exists in the gfs2 git tree -- both things that most
> people don't want to use, or are difficult to use.
>
> The RHEL5 branch has also been largely unusable for a long time, because
> it requires the RHEL5.1 kernel to build it, which isn't generally
> available AFAIK, much less widely in use.
>
> The STABLE2 branch will:
> - work with the latest stable upstream kernel from kernel.org
> - work with the whitetank branch of openais
> - otherwise have the same code/patches as the RHEL5 branch
>
> I think we should probably branch STABLE2 off of HEAD and then back out
> the changes that don't agree with the points above. The reason we've been
> putting this off is because of the pain of checking changes into another
> branch. I'm hoping to come up with some way to manage and track this with
> less manual intervetion, maybe even automate it to some extent.
I'm hoping that we can switch to git on sourcware.org prior to doing the
STABLE2 branch.
Given a STABLE2 git branch, another new branch for Fedora would be a short
and easy step away (there's a chance that STABLE2 itself may work for
Fedora.)
Dave
prev parent reply other threads:[~2007-10-09 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 21:40 [Cluster-devel] time for STABLE2 branch David Teigland
2007-09-18 21:43 ` [Cluster-devel] " David Teigland
2007-09-19 7:14 ` [Cluster-devel] " Patrick Caulfield
2007-10-09 16:26 ` David Teigland [this message]
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=20071009162634.GA2632@redhat.com \
--to=teigland@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).