update, to reflect http://lists.debian.org/debian-kernel/2007/03/msg00276.html
← Revision 19 as of 2009-03-16 03:31:04
converted to 1.6 markup
|Deletions are marked like this.||Additions are marked like this.|
|Line 3:||Line 3:|
|[http://lists.debian.org/debian-kernel/2005/09/msg00481.html debian-kernel mailing list]||[[http://lists.debian.org/debian-kernel/2005/09/msg00481.html|debian-kernel mailing list]]|
|Line 5:||Line 5:|
|[http://lists.debian.org/debian-devel-announce/2005/09/msg00002.html user tags]||[[http://lists.debian.org/debian-devel-announce/2005/09/msg00002.html|user tags]]|
|Line 7:||Line 7:|
|Line 17:||Line 17:|
|[http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=linux-2.6;firstname.lastname@example.org Buglist with d-kernel tags].||[[http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=linux-2.6;email@example.com|Buglist with d-kernel tags]].|
|Line 21:||Line 21:|
|* '''dkt-etch-update''', '''dkt-sarge-update'''|| * '''dkt-etch-update''' [[http://firstname.lastname@example.org;which=tag&data=dkt-etch-update|query]]
* '''dkt-sarge-update''' [[http://email@example.com;which=tag&data=dkt-sarge-update|query]]
It is hoped that this wiki entry will form the documentation for the usage of such tags, what they are and what they mean. below is a start on that.
These are in order to help maintain the kernels in accordance with the DebianKernelPatchAcceptanceGuidelines
Fixes targeted for a stable release
When the fix is pending in our repository
dkt-pending-package-removal: A removal of this package from the dists affected by this bug is planned, but hasn't taken place yet. This could be because we have dependencies keeping this package in said dist(s), or because we're waiting for our removal request to be acted upon by the ftp masters.
dkt-pending-new-upstream: This bug has been fixed upstream, and we'll include that fix when that upstream release is packaged. This is for things that are either dkt-backport-too-hard, or trivial enough to ignore until then.
When the problem is upstream and there is not much that can be done
dkt-unimplemented: The bug relates to a feature or enhancement that is not implemented in the upstream kernel. This is typically used in conjunction with the wontfix and upstream tags.
dkt-work-in-progress-upstream: The bug relates to a problem that is currently being worked on by the upstream kernel maintainers. See also dkt-work-in-progress below. This is typically used in conjunction with the upstream tag.
dkt-backport-too-hard: The bug relates to a problem that is fixed upstream but the backport is too difficult or extensive for incoportation into the debian kernel. See also dkt-backport below.
When the problem is being resolved by the Debian kernel team
In the case of these tags, it is useful to also set the owner field to the member or members of the kernel team that are working on the problem.
dkt-work-in-progress: The bug relates to work that is currently being done by the Debian kernel-team. This would typically be a bug that is also tagged dkt-work-in-progress-upstream, or a problem that is specific to the debian kernel such as a packaging or kernel config problem.
dkt-backport: The bug relates to a problem that is fixed upstream and should be backported to the debian kernel. See also dkt-backport-too-hard above.
Please also note that when the wontfix tag is used, it generally means can't fix with a reasonable amount of effort.