Releases

From Cluster Labs

Jump to: navigation, search

See also: Release Testing


Contents

Download

Binary packages for most 'rpm-based distributions (openSUSE, SLES, RHEL, CentOS) can be found at

 http://www.clusterlabs.org/rpm/

Simply browse for your distribution, download and install the relevant repository file. Instructions for this are included on our installation page.

Alternatively, the latest source can be found at:

 http://hg.clusterlabs.org/pacemaker/stable-1.0/archive/tip.tar.bz2

For further information and options for Debian/Ubuntu users, please see the installation page


Long Term Stable Releases

Even numbered release series (eg. 0.6.x, 1.0.x) are considered stable and will receive bug fixes but no additional features. These release series are recommended for production clusters.

Stable releases happen about once a month depending on the number and severity of the bugs fixed since the previous release. We understand that it is unlikely people will update their cluster every month, however often someone else has encountered the same problem you are (or will soon be) experiencing and the fix is included in a more recent version. Please consider this when deciding how often to upgrade your cluster software.

Feature Releases

Odd numbered release series (eg. 0.7.x, 2.1.x) are feature release. Their primary purpose is feature evaluation and bug discovery before a new stable series is released.

Things that might happen in an unstable release series:

  • features added
  • features removed
  • some features may be incomplete
  • the behavior of features may change
  • the configuration syntax may change
  • there will probably be more bugs than usual

Which can sound a bit scary, but the more people try it out, the more likely things will be usable, functional and bug-free when we lock everything down for the stable series that comes after it.

Although we spend a lot of time on testing, sometimes bugs slip through. The only way to guarantee the features that are important to you are bug free with your configuration is to try it with one of these releases.

Supported Branches

Version Current Release Tested Heartbeat Version First Released This Release Supported Until
1.1 NA 3.0.0 -- -- Q4 2010
1.0 1.0.7 3.0.0 Oct 9, 2008 Jan 18, 2010 Q4 2011 (at least)

Deprecated Branches

Version Last Release First Released Last Released
0.7 0.7.3 June 25, 2008 Sep 22, 2008
0.6 0.6.7 Jan 16, 2008 Dec 15, 2008

Release Calendar

Version Planned Actual
1.0.0 -- Oct 9, 2008
1.0.1 -- Nov 18, 2008
1.0.2 -- Feb 16, 2009
1.0.3 -- Apr 7, 2009
1.0.4 -- Jun 5, 2009
1.0.5 -- Aug 10, 2009
1.0.6 -- Nov 2, 2009
1.0.7 Jan 2010 Jan 18, 2010
1.0.8 Mar 2010
1.1.1 Mar 2010
1.1.2 May 2010
1.0.9 June 2010
1.1.3 July 2010
1.0.10 Sept 2010
1.1.4 Oct 2010
1.1.5 Dec 2010

Notes:

  • Releases are generally planned to occur on-or-about the 15th of the indicated month.
  • Feature releases, such as 1.1, will sync with devel on the no later than the 1st of the indicated month.


See Also: Upgrade Strategies

Personal tools
communication