[packagekit] Tracking a stable branch

[Richard Hughes]

In Fedora we will be shipping 0.1.x for Fedora 9 - rather than the
instability of git master.

The ABI/API churn of master is intentional, and allows us to move the
project forward quickly without any cruft, but isn't very suitable for
shipping to end users.

I've therefore created a remote branch in each project tree,
PACKAGEKIT_0_1_X and GNOME_PACKAGEKIT_0_1_X.

To get them to do:

git pull
git branch --track PACKAGEKIT_0_1_X origin/PACKAGEKIT_0_1_X
git checkout PACKAGEKIT_0_1_X

If you want to make a change, please be _very_ careful - this branch
will go into distros and breaking it will be frowned upon. Either commit
a patch as normal when you are on the branch, or if it's a trivial fix
that can be cherry picked, just do:

git cherry-pick ca1ca0a8c85a376e8a54eece8ae0ce9658964c0c

Now, the rules:

 * No new features in the stable branch
 * No new API in the stable branch
 * No cleanup patches in the stable branch
 * Don't put anything in stable that isn't in trunk
 * If you're not sure if to backport something, ask

I'll be releasing 0.2.0 in a few weeks, so please continue development
in master as per usual.
The ONLY point of committing to PACKAGEKIT_0_1_X is if you are a distro
maintainer creating .debs and .rpms - normal developers don't need to do
anything differently.

Richard.