Releases

From ClusterLabs

See also: Release Testing

Contents 1 Download 2 Long Term Stable Releases 3 Feature Releases 4 Supported Branches 5 Deprecated Branches 6 Release Calendar

Download

Binary 1.0.x packages for most rpm-based distributions (openSUSE, SLES, RHEL, CentOS) can be found at:

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

and for 1.1.x at:

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

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 w/ Glue	Tested w/ Corosync	Tested w/ Heartbeat	First Released	This Release	Supported Until
2.0	NA	TBA	TBA	TBA	August 22, 2012	TBA	TBA
1.1	1.1.8	NA	1.4, 2.1.0	-	Jan 15, 2010	Sep 20, 2012	December 2012
1.0	1.0.11	1.0.6	1.3.0	3.0.3	Oct 9, 2008	April 29, 2011	Q3 2012 (approx)

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
0.6.0	--	2008, Jan 16
0.6.1	--	2008, Feb 11
0.6.2	--	2008, Feb 14
0.6.3	--	2008, Apr 23
0.6.4	--	2008, May 22
0.6.5	--	2008, Jun 19
0.6.6	--	2008, Aug 24
0.6.7	--	2008, Dec 15
1.0.0	--	2008, Oct 9
1.0.1	--	2008, Nov 18
1.0.2	--	2009, Feb 16
1.0.3	--	2009, Apr 7
1.0.4	--	2009, Jun 5
1.0.5	--	2009, Aug 10
1.0.6	--	2009, Nov 2
1.0.7	2010, Jan	2010, Jan 18
1.0.8	2010, Mar	2010, Mar 16
1.0.9	2010, June	2010, Jun 23
1.0.10	2010, Oct	2010, Nov 12
1.0.11	2011, Mar	2011, April 29
1.0.12	2011, Sept	2011, Nov 24
1.0.13	2012, May
1.0.14	2012, Nov
1.1.1	2010, Mar	2010, Mar 05
1.1.2	2010, May	2010, May 12
1.1.3	2010, July	2010, Sept 21
1.1.4	2010, Nov	2010, Oct 20
1.1.5	2011, Jan	2011, Feb 11
1.1.6	2011, Apr	2011, Aug 31
1.1.7	2011, Nov	2012, Mar 29
1.1.8	2012, Jul
1.1.9	2012, Oct
1.2.0	2012, Dec

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