ATTENTION

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

Please, go to http://hg.linux-ha.org/[2] 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/[2] for list of available branches.

CVS for Linux-HA

To get read-only access to the Linux-HA CVS[3] 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[4].

CVS automated build script

We have written a script[5] 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[6], CVS commit mailing list[7], the original announcement mail[8], DownloadSoftware[9]

---

This information provided courtesy of the Linux-HA project at http://linux-ha.org/