[Cluster-devel] ATTENTION packagers and developers! (moving from 3.0.x to 3.1)

[Steven Whitehouse]

Hi,

To explain a bit more about what is happening on the GFS2 side of
things, this is our current plan:

 o gfs2-utils becomes its own package (with essentially identical
contents)
 o gfs2-cluster is a binary subpackage of gfs2-utils which will contain
the gfs2 related parts of the old cman package
 o The old cman pakage retains its original contents, minus what is now
in gfs2-cluster

So what is new in gfs2-cluster? Only gfs_controld and its associated man
pages, a new initscript and a gfs_control binary. The gfs2-cluster
package depends upon cman in order to ensure that dlm_controld etc are
also available.

As a result of being able to build the packages from the gfs2-utils git
tree (rather than the cluster tree which is currently used) that will
result in the tunegfs2 utility being added to gfs2-utils package at long
last.

The reason for wanting to make the split from the GFS2 side of things is
to allow independent (and more frequent) builds of gfs2-utils and thus
to keep the packages much more uptodate with respect to the head of the
tree,

Steve.


On Wed, 2010-10-06 at 15:39 +0200, Fabio M. Di Nitto wrote:
> -----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-----
>