From nobody Sun Feb 8 20:28:59 2026 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 207.211.31.81 as permitted sender) client-ip=207.211.31.81; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-delivery-1.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 207.211.31.81 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1586440544; cv=none; d=zohomail.com; s=zohoarc; b=XCs6Eg3TBODdtDKTQNPbdrGOe8TtSJ1MXf3gKZsRAIYknwxLXbgwQgyGW9tXEKvOMW5qdTXQB4RskahJnCbO5lUAgVA742Er6ch2XbOVXlDGZrfgyaMXMKZO+VeKXi1VIrd/PtXdgPRpxLBG+cAg5FRX4rVOz8D0I7chr+4JaYA= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1586440544; h=Content-Type:Content-Transfer-Encoding:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To; bh=O4+VNrNCzhPaBT70B5g/+Cyk9a+feUMUip5/9an7g4w=; b=d0ra7ZiRQoPnCQH2VhHw7S5np62228VfyG22LK55m5kz5mlaC9i0pq6BDIx9IpmBf6ydLbTsIF9CYKBiWI77lEqgYrXQJnsXTu65zUT0ykgFXny7L7dLUWmZf5vMl9ma6xVhrik/SO23KnPpMMIfKfeu+glSSM6qxblKFHa0S9c= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 207.211.31.81 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass header.from= (p=none dis=none) header.from= Return-Path: Received: from us-smtp-delivery-1.mimecast.com (us-smtp-2.mimecast.com [207.211.31.81]) by mx.zohomail.com with SMTPS id 1586440544323866.2274650882405; Thu, 9 Apr 2020 06:55:44 -0700 (PDT) Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-95-hXSAiE4PP3KHKOcPSm7qhQ-1; Thu, 09 Apr 2020 09:55:39 -0400 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id AE62413FF; Thu, 9 Apr 2020 13:55:31 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 770CC10027B3; Thu, 9 Apr 2020 13:55:31 +0000 (UTC) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id 271A018089D0; Thu, 9 Apr 2020 13:55:31 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 039DtOgK032211 for ; Thu, 9 Apr 2020 09:55:24 -0400 Received: by smtp.corp.redhat.com (Postfix) id 9A8D2B19AA; Thu, 9 Apr 2020 13:55:24 +0000 (UTC) Received: from localhost.localdomain.com (unknown [10.36.110.6]) by smtp.corp.redhat.com (Postfix) with ESMTP id CF092CFDE3; Thu, 9 Apr 2020 13:55:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1586440543; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=O4+VNrNCzhPaBT70B5g/+Cyk9a+feUMUip5/9an7g4w=; b=YFsl5kJEBhsyW/xqvYHeP9H9r9s+vu8OVBOAafheeddKivwFCyb8o0Mk7nVq6uX6Az7RGs iXAAA1M4s+piq52yub2N+nOjbMKDMI0SdksZAxUi3J0891fVDXSdRjj9x4gJ3Dp2K03NRz fXcjNYl/VgCu11SDT2IeqP4981WBIxE= X-MC-Unique: hXSAiE4PP3KHKOcPSm7qhQ-1 From: =?UTF-8?q?Daniel=20P=2E=20Berrang=C3=A9?= To: libvir-list@redhat.com Subject: [libvirt PATCH 1/6] docs: point users to gitlab for issue tracking Date: Thu, 9 Apr 2020 14:55:04 +0100 Message-Id: <20200409135509.1267947-2-berrange@redhat.com> In-Reply-To: <20200409135509.1267947-1-berrange@redhat.com> References: <20200409135509.1267947-1-berrange@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-loop: libvir-list@redhat.com X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: libvir-list-bounces@redhat.com Errors-To: libvir-list-bounces@redhat.com X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) Content-Type: text/plain; charset="utf-8" Currently we use the "Virtualization Tools" product in Red Hat Bugzilla for issue tracking upstream. This changes to point people to GitLab for issue tracking. Note that Bugzilla still has plenty of bugs present against libvirt. Triaging these to determine what is still valid will be a separate exercise. Bugzilla will be locked to prevent creation of new issues meanwhile. Signed-off-by: Daniel P. Berrang=C3=A9 Reviewed-by: J=C3=A1n Tomko --- docs/best-practices.rst | 5 +++-- docs/bugs.html.in | 27 ++++++++++++++------------- 2 files changed, 17 insertions(+), 15 deletions(-) diff --git a/docs/best-practices.rst b/docs/best-practices.rst index 7c48ff10be..4a28b03b65 100644 --- a/docs/best-practices.rst +++ b/docs/best-practices.rst @@ -15,8 +15,9 @@ with minimal back-and-forth. by any longer description of why your patch makes sense. If the patch fixes a regression, and you know what commit introduced the problem, mentioning that is useful. If the patch resolves a - bugzilla report, mentioning the URL of the bug number is - useful; but also summarize the issue rather than making all + upstream bug reported in GitLab, put "Fixes: #NNN" in the commit + message. For a downstream bug, mention the URL of the bug instead. + In both cases also summarize the issue rather than making all readers follow the link. You can use 'git shortlog -30' to get an idea of typical summary lines. =20 diff --git a/docs/bugs.html.in b/docs/bugs.html.in index 5534223384..c717fa813d 100644 --- a/docs/bugs.html.in +++ b/docs/bugs.html.in @@ -19,7 +19,7 @@ security process instead.

=20 -

Bug Tracking

+

Bug Tracking

=20

If you are using libvirt binaries from a Linux distribution @@ -30,22 +30,17 @@

General libvirt bug reports

=20

- The Red Hat Bugzilla Server - should be used to report bugs and request features in libvirt. + Bugs in upstream libvirt code should be reported as issues in + the appropriate GitLab project= . Before submitting a ticket, check the existing tickets to see if the bug/feature is already tracked. - - For general libvirt bug reports, from self-built releases, GIT snaps= hots - and any other non-distribution supported builds, enter tickets under - the Virtualization Tools product and the libvirt<= /code> - component.

It's always a good idea to file bug reports, as the process of filing the report always makes it easier to describe the problem, and the bug number provides a quick way of referring to - the problem. However, not everybody in the community pays - attention to bugzilla, so after you file a bug, asking questions + the problem. However, not everybody in the community pays frequent + attention to issues, so after you file a bug, asking questions and submitting patches on the libvirt mailing lists will increase your bug's visibility and encourage people to think about your problem. Don't hesitate to @@ -65,10 +60,16 @@

=20 =20 +

+ Note bugs in language bindings and other sub-projects should be + reported to their corresponding git repository rather than the + main libvirt.git linked above. +

+

Linux Distribution specific bug reports=

  • @@ -85,7 +86,7 @@ If you are using binaries from Red Hat Enterprise Linux, enter tickets against the Red Hat Enterprise Linux product that you're using (e.g., Red Hat Enterprise - Linux 6) and the libvirt component. Red Hat + Linux 8) and the libvirt component. Red Hat bugzilla has additional g= uidance about getting support if you are a Red Hat customer.

    --=20 2.24.1