|
|
|
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
|
|
|
|
--------
|
|
|
|
|
|
|
|
The repository has three types of branches:
|
|
|
|
1. The `master` branch, which tracks the latest greatest upstream version.
|
|
|
|
2. Branches to track different Debian releases (`sid`, `buster`,
|
|
|
|
`buster-security`, etc).
|
|
|
|
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. Have a
|
|
|
|
look at [their git
|
|
|
|
repository](https://anonscm.debian.org/cgit/kernel/linux.git) to see it in
|
|
|
|
action with quite some history already.
|
|
|
|
|
|
|
|
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 `sid`
|
|
|
|
branch), we can already work on getting 4.11 packaging in shape in the master
|
|
|
|
branch.
|
|
|
|
|
|
|
|
Contributing
|
|
|
|
------------
|
|
|
|
|
|
|
|
There are many ways to contribute to this project. Think about how you want to
|
|
|
|
participate. It's up to you to decide in whatever way you want to help. Find
|
|
|
|
out what you can/want to do, and then be committed to it.
|
|
|
|
|
|
|
|
* Report bugs or missing features in the BTS.
|
|
|
|
* Reply to bugs in the BTS, trying to get issues more clear, reproduce them
|
|
|
|
yourself and/or find a fix.
|
|
|
|
* Clone the repository, fix bugs and submit patches to the mailing list for
|
|
|
|
review.
|
|
|
|
* Join or start discussions on the mailing list or in gitlab issues about new
|
|
|
|
ideas for improvements.
|
|
|
|
* Contribute a bigger feature to the packaging and also be there when users
|
|
|
|
submit bug reports. ;-)
|
|
|
|
* 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://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-xen-devel)
|
|
|
|
* IRC: `#debian-xen` on OFTC
|
|
|
|
* [The Debian BTS](https://bugs.debian.org/src:xen)
|
|
|
|
|
|
|
|
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 Freenode |
