|
|
|
Xen packaging for Debian
|
|
|
|
========================
|
|
|
|
|
|
|
|
Welcome to the documentation of the Debian Xen Team.
|
|
|
|
Welcome to the Debian Xen Team.
|
|
|
|
|
|
|
|
The Debian Xen Team consists of a group of people that use Xen on Debian
|
|
|
|
systems.
|
|
|
|
|
|
|
|
The main tasks are to keep up with newest Xen versions for Debian
|
|
|
|
testing/unstable, and making sure security updates for Debian stable get done
|
|
|
|
in a timely manner.
|
|
|
|
|
|
|
|
Besides this, based on any 'bandwidth' available in the team, we work on
|
|
|
|
improvements in the packaging or documentation.
|
|
|
|
|
|
|
|
We try to keep the barrier to participation as low as possible. If you're a
|
|
|
|
Debian and Xen user, and want to know a bit more about it, except for just
|
|
|
|
being a user of the packages, or, if you want to meet some other users, feel
|
|
|
|
free to just say hello on IRC and ask around what's happening.
|
|
|
|
|
|
|
|
Contact
|
|
|
|
-------
|
|
|
|
|
|
|
|
* IRC: `#debian-xen` on OFTC. This is the main place to get into contact. Don't
|
|
|
|
wait for activity in the channel, just start by saying Hi, or asking a
|
|
|
|
question.
|
|
|
|
* [pkg-xen-devel mailing list](https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-xen-devel)
|
|
|
|
* [debian-xen mailing list](https://lists.debian.org/debian-xen/), that we want to use instead of the alioth one.
|
|
|
|
* [The Debian BTS](https://bugs.debian.org/src:xen)
|
|
|
|
|
|
|
|
Branches
|
|
|
|
--------
|
|
|
|
|
|
|
|
The repository has three types of branches:
|
|
|
|
The [Debian Xen packaging
|
|
|
|
repository](https://salsa.debian.org/xen-team/debian-xen/-/branches) has three
|
|
|
|
types of branches:
|
|
|
|
1. The `master` branch, which tracks the latest work for unstable (sid).
|
|
|
|
2. Branches to track different Debian releases (`experimental`, `buster`,
|
|
|
|
`buster-security`, etc).
|
|
|
|
3. Team member branches, `<user>/*` (e.g. `knorrie/blaat-mekker`) are branches
|
|
|
|
3. 'Work in Progress' (`wip/*`) branches which relate to the ones mentioned
|
|
|
|
above. So, for example there is a `wip/sid` branch, in which we might be
|
|
|
|
busy preparing a new package version. As soon as the upload is done, we
|
|
|
|
merge it to the actual `master` branch.
|
|
|
|
4. Team member branches, `<user>/*` (e.g. `knorrie/blaat-mekker`) are branches
|
|
|
|
where team members can mess around, share ideas, share work for review etc.
|
|
|
|
|
|
|
|
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.
|
|
|
|
So even if for example Xen 4.10 is in unstable (getting updates in the `master`
|
|
|
|
branch), we can already work on getting 4.11 packaging in shape in the
|
|
|
|
So even if for example Xen 4.17 is in unstable (getting updates in the `master`
|
|
|
|
branch), we can already work on getting 4.18 packaging in shape in the
|
|
|
|
`experimental` branch.
|
|
|
|
|
|
|
|
Contributing
|
| ... | ... | @@ -40,14 +71,6 @@ out what you can/want to do, and then be committed to it. |
|
|
|
* Or just clone the repository and use it as a base for your own modified
|
|
|
|
packages with extra upstream patches, etc.
|
|
|
|
|
|
|
|
Contact
|
|
|
|
-------
|
|
|
|
|
|
|
|
* [pkg-xen-devel mailing list](https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-xen-devel)
|
|
|
|
* [debian-xen mailing list](https://lists.debian.org/debian-xen/)
|
|
|
|
* IRC: `#debian-xen` on OFTC
|
|
|
|
* [The Debian BTS](https://bugs.debian.org/src:xen)
|
|
|
|
|
|
|
|
Moar links
|
|
|
|
----------
|
|
|
|
|
| ... | ... | @@ -59,4 +82,4 @@ Upstream |
|
|
|
|
|
|
|
* [xen-users mailing list](https://lists.xenproject.org/mailman/listinfo/xen-users)
|
|
|
|
* [xen-devel mailing list](https://lists.xenproject.org/mailman/listinfo/xen-devel)
|
|
|
|
* IRC: `#xen` on OFTC |
|
|
|
* IRC: `#xen` and `#xendevel` on OFTC |
