Looking for current and maintained information and documentation on (Linux ) Open Source High Availability HA Clustering?You probably should be reading the Pacemaker site clusterlabs.orgThis site conserves Heartbeat specific stuff. See Site news for details.

Contributing to Debian development

In line with Debian policy, .deb packaging instructions are not included in the upstream Mercurial repositories. Instead, the Debian packagers track their changes in Mercurial repositories on alioth.debian.org, where they are maintained in per-release branches.

Notes for Debian Developers

If you are a Debian Developer in the debian-ha team, you have push access to the Mercurial repositories on alioth. To set things up, please follow these steps:

Below is an example for working with the cluster-glue repository. However, the same procedure must be followed for the heartbeat and cluster-agents repositories.

Make your modifications, issuing hg commit after each one. Be sure to include a meaningful changeset description. When you are done, you can issue the following command to get an overview of those changesets present in your local working directory, but not yet pushed to alioth:

hg outgoing debian

Finally, you can push your changes:

hg push debian -r sid

Tracking upstream

At certain points, you will want to import all changes to upstream into the Debian branches (this will typically occur after upstream releases). To do so, again, use merging. For example, if you want to create a new sid package because a release has happened upstream, proceed as follows:

Switch to the sid branch:

hg update -C sid

Pull from upstream and update your working directory to a tagged release:

Make any necessary changes to Debian packaging. Again, commit them in logical chunks, with meaningful commit messages. Then, push the changes to alioth:

hg outgoing debian -r sid
hg push debian -r sid

Notes for non-DDs

If you are not a Debian Developer, you can still help with Debian packages! You will not be able to push directly into the Debian repositories, but you can still submit patches which the Debian maintainers can then incorporate into their packaging.

Below is an example for working with the cluster-glue repository. However, the same procedure should be followed for the heartbeat and cluster-agents repositories.

Create a working directory

First, create a working directory cloned from the Debian repository:

hg clone http://hg.debian.org/hg/debian-ha/cluster-glue

Fetch branches

Next, fetch the Mercurial branch for the distribution where you wish to contribute (in this example, sid)

Make your modifications, issuing hg commit after each one. Be sure to include a meaningful changeset description. When you are done, you can issue the following command to get an overview of those changesets present in your local working directory, but not in the repository on alioth: