From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 13A9DC4332F for ; Thu, 29 Sep 2022 19:00:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229899AbiI2TAP (ORCPT ); Thu, 29 Sep 2022 15:00:15 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58258 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229866AbiI2TAM (ORCPT ); Thu, 29 Sep 2022 15:00:12 -0400 Received: from premium237-5.web-hosting.com (premium237-5.web-hosting.com [66.29.146.205]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D283732D90; Thu, 29 Sep 2022 12:00:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sladewatkins.net; s=default; h=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=eb0khICbQDL4+jyyr8c6E6L4E4XS0/81ahtM8QIqTzo=; b=UrW1D3nlrRLAddd5YLM8QMUKUO VJ6k9TO6qjLzi7BhaH49aB3G+Aqk0sS/ySSbtZmvVhxAJbX3JgZ/HO2KlOU4U9xQM/e67XmslWzkj ZfxZ6POs9H2CgfQhQvtUm5baBZG5W70OvzoO2oBDSvR23QwlRWZ+L7ORm/RZJsN4MWg6MbKL0DnZT cVgq+1PWpnsAfboZ+Hh5IDqejG0gA3hyt0A8M/Ry6FOK/Er5h0iAXnbPiJFFUJ/jONfz9We85iu8i 8mmH5jR4T6qFAafUvs9tSYEpJVfm5UhXT/X5J5BOZuDwyJyDFw7kmf5BWNRk6pWXBBxPo6sNyDzka IuTIUnxg==; Received: from pool-108-4-135-94.albyny.fios.verizon.net ([108.4.135.94]:54336 helo=smtpclient.apple) by premium237.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1odylQ-003C8d-CP; Thu, 29 Sep 2022 15:00:04 -0400 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\)) Subject: Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla blues" From: Slade Watkins In-Reply-To: Date: Thu, 29 Sep 2022 15:00:00 -0400 Cc: "Artem S. Tashkinov" , Konstantin Ryabitsev , Thorsten Leemhuis , workflows@vger.kernel.org, LKML , Greg Kroah-Hartman , Linus Torvalds , "regressions@lists.linux.dev" , ksummit@lists.linux.dev Content-Transfer-Encoding: quoted-printable Message-Id: <49D9FA95-4C73-40BA-A112-93DDFD77D1A2@sladewatkins.net> References: <05d149a0-e3de-8b09-ecc0-3ea73e080be3@leemhuis.info> <93a37d72-9a88-2eec-5125-9db3d67f5b65@gmx.com> <20220929130410.hxtmwmoogzkwcey7@meerkat.local> <7b427b41-9446-063d-3161-e43eb2e353f9@gmx.com> <20220929135325.4riz4ijva2vc7q5p@meerkat.local> <95c3384b-53d0-fd6c-6ec5-a7e03fdeddfc@gmx.com> To: Laurent Pinchart X-Mailer: Apple Mail (2.3696.120.41.1.1) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - premium237.web-hosting.com X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - sladewatkins.net X-Get-Message-Sender-Via: premium237.web-hosting.com: authenticated_id: srw@sladewatkins.net X-Authenticated-Sender: premium237.web-hosting.com: srw@sladewatkins.net X-Source: X-Source-Args: X-Source-Dir: X-From-Rewrite: unmodified, already matched Precedence: bulk List-ID: X-Mailing-List: workflows@vger.kernel.org Hey there, > On Sep 29, 2022, at 12:42 PM, Laurent Pinchart = wrote: >=20 > E-mails are not that bad to report issues, but they can't provide the > core feature that any bug tracker oughts to have: tracking. There's no > way, with the tools we have at the moment (including public-inbox, b4 > and lei), to track the status of bug reports and fixes. Even for = patches > we need to rely on patchwork, and that's far from perfect. Yeah, I (sort of) changed my mind on this [1], but you=E2=80=99re right: = it lacks tracking issues from reported-to-fixed, and unless something = was engineered specifically for it, we=E2=80=99re out of luck. >=20 > I agree with the comment that was repeated multiple times: it's quite > pointless to improve the tooling if we don't first improve the = process, > and find a way to allocate people and time to handling bug reports. = Even > if bugzilla has reached EOL upstream, and even if it isn't perfect, = the > instance runs today, and gives us a tracker that could be used to = design > a proper process and implement it, should we desire to do so. There's = no > chicken-and-egg issue to be solved where lack of tooling would prevent > the implementation of a bug tracking process. I'm quite confident = that, > if we manage to implement a bug tracking process, we will find a way = to > get the tooling we need, be it through bugzilla or something else. Right.=20 To be honest, I think the best move from here is improve the process = first, then worry about everything else when the time comes. Can=E2=80=99t= really go any further without first addressing the process in my = opinion. The important thing to remember is that nothing implemented = will ever be "perfect.=E2=80=9D That=E2=80=99s just not possible. = However, we _can_ make something that=E2=80=99ll work and continue = refining it over time.=20 [1] = https://lore.kernel.org/lkml/C4935ACC-65C8-4705-B9FF-A1CA0A648B9D@sladewat= kins.net/ Cheers, -srw