| ... | ... | @@ -3,12 +3,6 @@ Xen packaging for Debian |
|
|
|
|
|
|
|
Welcome to the documentation of the Debian Xen Team.
|
|
|
|
|
|
|
|
Building the package
|
|
|
|
--------------------
|
|
|
|
|
|
|
|
Instructions to build a package are included in the README.source in the
|
|
|
|
packaging code.
|
|
|
|
|
|
|
|
Branches
|
|
|
|
--------
|
|
|
|
|
| ... | ... | @@ -19,14 +13,7 @@ The repository has three types of branches: |
|
|
|
3. Team member branches, `<user>/*` (e.g. `knorrie/blaat-mekker`) are branches
|
|
|
|
where team members can mess around, share ideas, share work for review etc.
|
|
|
|
|
|
|
|
When an upload is done, the release commit gets a signed tag with the debian
|
|
|
|
version number.
|
|
|
|
|
|
|
|
Note: Yes, this way of working is copied from the Debian Kernel Team (except of
|
|
|
|
using the master branch for tracking unstable instead of experimental. Have a
|
|
|
|
look at [their git
|
|
|
|
repository](https://salsa.debian.org/kernel-team/linux/branches) to see it in
|
|
|
|
action with quite some history already.
|
|
|
|
The packaging style is based on `git-debrebase`.
|
|
|
|
|
|
|
|
When a new upstream version is in release candidate stage, we can target Debian
|
|
|
|
experimental for uploads to allow Debian users to help testing the new release.
|
| ... | ... | |
