All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] ATTENTION packagers and developers! (moving from 3.0.x to 3.1)
Date: Wed, 06 Oct 2010 15:39:17 +0200	[thread overview]
Message-ID: <4CAC7C05.7020607@redhat.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi all,

either today or tomorrow, we will release 3.0.17 (that unless will show
major issues) it will be the last release of cluster in the 3.0.x series.

The next release will be 3.1.0 and it will be the first release gearing
towards the split git trees.

With 3.1.x release, we will:

- - drop any gfs/gfs2 related code from cluster project.
- - drop fence agents from cluster project.
- - drop resource agents from cluster project.

The gfs2 code will be released from gfs2-utils.git.
The fence agents will be released from fence-agents.git
The resource agents will be released from resource-agents.git

We will clearly synchronize the first release to avoid any regression,
but from there on, the 4 projects will release independently (unless
big changes will require otherwise).

Due to the nature of the changes, 3.1 will come out when it?s ready, so
it might take slightly longer than the usual month in between releases.

Cheers,
Fabio
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJMrHwDAAoJEFA6oBJjVJ+O5sIQALrf/SjrkBwM2bixjwLDLrdH
swXkqZRv/ycU1QvoW6Hw/jCsvq/i/8ieNrjtTqgNpuhrGIv4mjATdz41s72ehQxl
VRmPmkqeUC9tDXXxlaF6V0t2it0TvTO6QjtrHPq+Q2pSr66vV1JHJTlC+jiYLPG4
jlUkPB1R+nomli64votMpnYdSjRHwCDB4FeDPsoQBxCBRth86IzBX3Bnj5dsxGI3
yhwFHKpIV0mIy2qpj/D0KCzGLxwsU368HluHC+mmFJ2xeLKwYV/GuhPtBSG1GKds
P7k0Ll06vNn+YiIJMA24INGZtDesqho8NcADMHgbK97fRQ+ajgGiVAkukVChsdVb
tdCulotj8MNaumCGLpyvz4tPPGJpcFIUdJ5LSqB+VVn5I8vWWr93cDGczJexSihy
Cy7R6bcP9dzeiexnOW1t0yEv0TGUb0L6E85NzlygJrPqWjZadqXInbhD8q5302Ts
tRbPdL9D7n17l2JH2l8Cy2eq3P1Kb14RE4TBDeMID5rMMyRImUDs0NIZvtCPUZLF
D2ygvIgymMfgLcPpnHq0HlviQvnGBEU1jLMCnqmM1YUuwndD/8GQYWe5drwavGR8
WkQh0LfCfxI/doP4hP1NdMgcWnZwBUSf+aXE5RKVihjbdruxnr1BvDcxCsFNTJ47
D7ZbjBZBJ9wMz/F9VBpX
=jyu2
-----END PGP SIGNATURE-----



             reply	other threads:[~2010-10-06 13:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06 13:39 Fabio M. Di Nitto [this message]
2010-10-06 14:33 ` [Cluster-devel] ATTENTION packagers and developers! (moving from 3.0.x to 3.1) Steven Whitehouse

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=4CAC7C05.7020607@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 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.