Skip to content
Snippets Groups Projects

Home

Last edited by Hans van Kranenburg

Xen packaging for Debian

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

Branches

The Debian Xen packaging repository 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. '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.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

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.
  • Fork the repository, fix bugs or make changes and open a merge request on the Debian gitlab server Salsa.
  • 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.

Moar links

Upstream

Comments

    Please register or sign in to add a comment.