Hi,
On 23/05/17 15:12, Konrad Rzeszutek Wilk wrote:
The primary location for reporting bugs against the hypervisor and
associated bundled tools [...] is by posting to the xen-devel mailing
list (list info). Please tag your subject line with a '[BUG]' prefix.
Note that you do not need to be subscribed to the list to post
(although non-subscribers are moderated this usually happens pretty
quickly) and that list policy is to CC people so you shouldn't miss
any replies.
[...]
Although a bugzilla instance does exist it is not well maintained or
widely used by developers. If you really want to file a bug in
bugzilla you are strongly recommended to also post to the mailing
list.
This does not make things easier for us, because rather than recurrently
check a simple bug status field in the Xen tracker, we'd have to be
tapped into Xen development, and follow the email thread & any relevant
commits closely. In reality I'm not even subscribed to xen-devel.
We recently introduced a tracker ([1]) to help us following the state of
bugs/features. It is managed by maintainers and read-only for the others.
The usual process is to report the bug on the mailing-list and a
maintainer will create a bug on the tracker if we have no immediate
solution.
In this case, the patch made rc6. So I believe the problem is resolved.
Cheers,
[1] https://xenproject.atlassian.net/projects/XEN/issues
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
