Hans van Kranenburg
2018-Oct-24 18:20 UTC
[Pkg-xen-devel] Xen bug reports for Xen 4.1 and 4.4 (or even Xen 3.2)
Hi list, I'm planning to start responding to all bts bugs that we have that are related to Xen versions before Stretch. There's quite a few of those. If they're clearly a question about the packaging, like #862408, then I will skip those for now. But stuff like problems with upstream code or "I cannot boot my Windows ISO with qemu on lenny" (I just made that up as example) should go away. What I would propose is: * Make up some proper standard text which asks the bug submitter if she/he's still using this version and is still experiencing this problem. * Announce that we will close the bug after X time if there's no response. What about: """ Hi <Name of Reporter>, This is about the bug report that you filed before about <title> in the Debian bug tracker against the Xen packages. Your bug report was targeted at a Xen package in a Debian distribution older than the current stable (Stretch). When starting to deal again with bug reports that are already open for a longer time, we'd like to have the reporter of the bug confirm that she or he is still experiencing this problem, so we can spend the effort on the bugs in a directed way. Can you please help us by confirming that any of the following scenarios does apply to your situation? * I had this problem a long time ago. It was never solved, but I found a workaround, which is ... * I had this problem a long time ago, and I solved it by not using Xen any more, but by doing ... * I still experience this problem, and I'm still using Xen 3.2/4.1/4.4/etc. I cannot upgrade to Stretch because ... * I had this problem, and since upgrading to Stretch / Buster / ? it seems it was solved, and I forgot to report it again. Please close it, thanks. * <... what other options here? ...> * Other: ... Note that even if you found a solution, it's still very useful to report it back to our bug tracker. There might be someone else running into the same problem, who can be helped with your information. Please note that unless there's a response within a month from now, we will close it. If you discover this message later, and this case is important to you, then you can try unarchiving the bug and replying to it, or reach out to the maintainers email list at pkg-xen-devel at lists.alioth.debian.org (no subscription required) and post a message. Thanks, <My name Here> """
Diederik de Haas
2018-Oct-27 15:29 UTC
[Pkg-xen-devel] Xen bug reports for Xen 4.1 and 4.4 (or even Xen 3.2)
On woensdag 24 oktober 2018 20:20:01 CEST Hans van Kranenburg wrote:> When starting to deal again with bug reports that are already open for a > longer time, we'd like to have the reporter of the bug confirm that she > or he is still experiencing this problem, so we can spend the effort on > the bugs in a directed way.The last part of the sentence ("we can spend ...) gives me the impression that the Debian Xen maintainers will work to fix the issue. Given what you've written in the other mail (bug reports for upstream), my guess is that's probably not the impression you want to give. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part. URL: <http://alioth-lists.debian.net/pipermail/pkg-xen-devel/attachments/20181027/6d01fb90/attachment.sig>
Hans van Kranenburg
2018-Oct-27 22:24 UTC
[Pkg-xen-devel] Xen bug reports for Xen 4.1 and 4.4 (or even Xen 3.2)
On 10/27/2018 05:29 PM, Diederik de Haas wrote:> On woensdag 24 oktober 2018 20:20:01 CEST Hans van Kranenburg wrote: >> When starting to deal again with bug reports that are already open for a >> longer time, we'd like to have the reporter of the bug confirm that she >> or he is still experiencing this problem, so we can spend the effort on >> the bugs in a directed way. > > The last part of the sentence ("we can spend ...) gives me the impression that > the Debian Xen maintainers will work to fix the issue. > Given what you've written in the other mail (bug reports for upstream), my > guess is that's probably not the impression you want to give.Yeah. Reading back, that whole alinea can just be removed. It should be pretty obvious that limited resources should first be used to work on stable and testing instead of (((old)old)old)stable. Hans
Seemingly Similar Threads
- Bug#618576: xen-3.2-1: VNC display over HVM XEN 3/Lenny AMD64, displays a blank screen when Debian-Installer Squeeze AMD64 is running on it
- Bug#804884: xen-hypervisor-4.4-amd64: Starting with hypervisor get nouveau CACHE_ERROR in dmesg without hypervisor -> OK
- Xen packaging in Debian
- Bug#503046: xen-utils-3.2-1: inadequate error handling for the case of a failure to use a loopback device
- Bug#820807: xen-hypervisor-4.4-amd64: Xen detects only one CPU when bootet via EFI and grub2