This site best when viewed with a modern standards-compliant browser. We recommend Firefox Get Firefox!.

Linux-HA project logo
Providing Open Source High-Availability Software for Linux and other OSes since 1999.

USA Flag UK Flag

Japanese Flag

Homepage

About Us

Contact Us

Legal Info

How To Contribute

Security Issues

7th - 10th October 2008 Linux-Kongress in Hamburg will have several sessions on Linux-HA - see you there!

18 August 2008 Heartbeat release 2.1.4 is now out Download it

11 October 2007 NEW educational HA/DR Blog hosted by Alan Robertson

9 April 2007 Check out the Cool Heartbeat Screencasts: Installation, Intro to the GUI Part of the Heartbeat Education project

Last site update:
2008-10-12 18:56:14

ATTENTION

Linux HA has switched over to Mercurial as our source code management system. The text below is of historical interest only.

Please, go to http://hg.linux-ha.org/ instead.

Checking out the development branch

  • Make sure Mercurial is installed
  • Run

    hg clone http://hg.linux-ha.org/dev
    

See http://hg.linux-ha.org/ for list of available branches.

CVS for Linux-HA

To get read-only access to the Linux-HA CVS instance, here's what you do:

export CVSROOT=:pserver:guest@cvs.linux-ha.org:/home/cvs/linux-ha
cvs login
  • The password for user guest is guest

The module name is "linux-ha". Now, you can do normal CVS commands, and things should go well from there.

For example, one can do a cvs co linux-ha, and got a copy of the workspace. Once a copy is obtained, one can do a cvs update -d to see the latest changes to the repository.

Linux-HA CVS web interface

The CVS repository can be accessed via the web.

CVS automated build script

We have written a script for automating builds and simple tests from CVS. Some may find it useful, or interesting as a start for your own tool to do the same.

Use of Branches

We keep the development version of CVS as the HEAD branch. When we want to create a maintainable, stable release, we create a branch in CVS. We currently have the following branches:

  • HEAD

  • STABLE_1_2

  • STABLE_1_0

  • STABLE_0_4_9-branch

Tagging

We have a convention of tagging releases with STABLE_x_y_z for stable release x.y.z. Here are a few of those tags:

  • STABLE_1_2_3

  • STABLE_1_2_2

  • STABLE_1_2_1

  • STABLE_1_2_0

  • STABLE_1_0_4

  • STABLE_1_0_3

  • STABLE_1_0_2

  • STABLE_1_0_1

  • STABLE_0_4_9

We tag beta releases with BETA_a_b_c for beta release a.b.c. Here are a few of these tags from CVS:

  • BETA_1_99_5

  • BETA_1_99_4

  • BETA_1_99_3

  • BETA_1_99_2

  • BETA_1_99_1

See Also

ContactUs, CVS commit mailing list, the original announcement mail, DownloadSoftware