From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id ULe0DGMKRGVpYwEAG6o9tA:P1 (envelope-from ) for ; Thu, 02 Nov 2023 21:45:23 +0100 Received: from aspmx1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id ULe0DGMKRGVpYwEAG6o9tA (envelope-from ) for ; Thu, 02 Nov 2023 21:45:23 +0100 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id D0BB65090D for ; Thu, 2 Nov 2023 21:45:22 +0100 (CET) Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1698957923; a=rsa-sha256; cv=none; b=a2x3Ma0yv9I11pNbc8qPZXxp/V6qs4P5lcQRTjHiRUR4ZJOexP7LEAnZzZaJNm232WQUz4 dwr61hSbhK3kc1CpTfZtV1Eh1AmU6XqvHxojaUpp4mpJgu2fyxbae4lOF27lNGv4JoZQVq 5DnRmtCZweF8JAe2xAMSaLG2mesCiKH87Kvt3bLHlKikYCklE8j/KzlhIVUfaM+t59MdCR jcbhuLa9DuMImkrKfihpdBxPHaAb7lKqcZa+SmsI0l4jQiVuFFy+pZ2rRRLWMrDxyKqedb b9T+TlsEDJTbLzZyLEFFXxrrt9ej7VXPzts25dzHSErgoriOHYMLCRBXXVA2WA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1698957923; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post; bh=u3C250j/DTg71Xo5owlavh9tOV1o4CgQCIASQ2VwkUM=; b=cNa3HfnHrJmaISgXDoAyjEyPEnBj3yV1LZja0QiEh4l9j34sq8d8qbgOsFE+xtS7HUCTJw qwp029R/c67/kC+NfO1KacvJeubmCUVmC5u9OncO5xSQVb52UVKSlv7e9H2hRMlRo4q4d3 7KSqoLMefmungVubPK3M4IV6bYyqHNypgOrOPcc7TPlPwYg8K/YmbFH6uLLijnzWkjsvix 8XKnHe+ku2R7YhQ8vMI9/m27g3Sm4nsxziiCklZ6GIWvJWobIJg4NGuK2qr1/vEdiqSXuJ LIrPZkwcyip4JAtUEcVbeS5zp2sSbfV8Drrr13iX/odSyGmeec1Ac417/Z3Sfw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qyeYY-0006Fu-BF; Thu, 02 Nov 2023 16:44:46 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qyeYX-0006Fj-9c for guix-devel@gnu.org; Thu, 02 Nov 2023 16:44:45 -0400 Received: from mira.cbaines.net ([2a01:7e00:e000:2f8:fd4d:b5c7:13fb:3d27]) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qyeYU-0002CT-TK for guix-devel@gnu.org; Thu, 02 Nov 2023 16:44:45 -0400 Received: from localhost (unknown [193.96.224.61]) by mira.cbaines.net (Postfix) with ESMTPSA id 95B2C27BBE2; Thu, 2 Nov 2023 20:44:40 +0000 (GMT) Received: from felis (localhost [127.0.0.1]) by localhost (OpenSMTPD) with ESMTP id e913474c; Thu, 2 Nov 2023 20:44:37 +0000 (UTC) References: <8734xohzzy.fsf@> User-agent: mu4e 1.10.7; emacs 29.1 From: Christopher Baines To: Suhail Cc: guix-devel@gnu.org Subject: Re: August/November update on qa.guix.gnu.org and related things Date: Thu, 02 Nov 2023 20:19:06 +0000 In-reply-to: <8734xohzzy.fsf@> Message-ID: <87pm0ropfw.fsf@cbaines.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Received-SPF: pass client-ip=2a01:7e00:e000:2f8:fd4d:b5c7:13fb:3d27; envelope-from=mail@cbaines.net; helo=mira.cbaines.net X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Scanner: mx11.migadu.com X-Spam-Score: -8.21 X-Migadu-Queue-Id: D0BB65090D X-Migadu-Spam-Score: -8.21 X-TUID: 6trFOVNEptAI --=-=-= Content-Type: text/plain Suhail writes: > Christopher Baines writes: > >> - The README is published at https://qa.guix.gnu.org/README > > The README seems more focused on task planning and TODO items than > explaining how to use the qa.guix.gnu.org website. Could you please > provide a reference for the latter? There isn't much documentation for QA, mostly because I want to see it improve so that you don't need documentation to use it. > Specifically, I submitted a patch some while ago: > . Its QA status is marked as > unknown with a few items highlighted in red. While the UI helps draw > attention to those items, it's not clear (to me) how to remedy them and > who is responsible for doing what. I.e., what are the next steps? I > would like to get that patch reviewed and merged in some way, but I > don't know what, if anything, I can do to help with the matter. I had a look at the QA page for #66644 and yeah, the red highlighted bits where builds which hadn't happened yet. I think it's fair to say that these shouldn't be styled the same as failed builds, so I've changed the styling now. I've also added a new issue status for when QA is waiting on builds to happen to provide more information. So yeah, QA isn't currently pointing out anything for you to do on this issue. >> I'd also really like to see some testing of the patch review feature >> in QA, since I think trying to get people without commit access >> reviewing patches will really help speed up getting things reviewed >> and merged. > > Is there a document that outlines how to get started and/or > pre-requisites that one must have before reviewing certain aspects? On the page for each issue on qa.guix.gnu.org, there's a list of common things to check. That form gives a way to record a review when you think the patches look good to merge. There's also some content in the manual that might be useful when reviewing patches: https://guix.gnu.org/en/manual/devel/en/html_node/Packaging-Guidelines.html https://guix.gnu.org/en/manual/devel/en/html_node/Submitting-Patches.html But there's no pre-requisites to reviewing Guix patches, so the best way to learn is to start looking to review things. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKlBAEBCgCPFiEEPonu50WOcg2XVOCyXiijOwuE9XcFAmVECjNfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcRHG1haWxAY2Jh aW5lcy5uZXQACgkQXiijOwuE9XfubA/9F4DeWOVpYgmOMuweRiOdz1WwtkZsiRtR d27dSUDACWEVTk6yzENB89Dnqlvlf9ErbuI7zLsgcZFtlnvcG3OIlqlGZp6AzkAV sx3HyxvfMTrvfahlhWo8v34R1a8G82IxqGrT6Ta6hR5z/YVgNxCbsCgVDl1sVFEM ashMBwUOT5aGhMS/PMbWsUPe2qmIRimN6msS1J41yntyKld0IDWd0eXq/U54H1+l 16oe/tJGwYcjtdGxTiF6BfpJAY4s8f+ag2vOoN4QnZRGGgVVcmQpH8geyRiZq7r+ nJKJ7pAxElw7aopFxE+46IcguXytuIJwbA92KhH4NXhV9Qn2RwIreUZbt6RuSxYN nF11xlRD4I3MMr/2O9RpurCQxhhxnxhiw9VRDbMkm+FrIo+C7Xjt3V5vIcCcCi8m Ng4MoBsCA4rQRb6CqEfSwXJxUUcDBm5vncebqNNrCUL2ynwoQachaZoXbkOHgz5A nrmNQcw7SVoSBS6fVhe832VlxbNfEiGJM2bIQy4zs1iKg+RSx42iQ2efZYI/GL37 Bk67r5TlbV9399I9rQY4QJDQyzM6k/Cv2wi5vpw2ROnrY4SW6OZlRqBc73/j5zur Jlp+f9npmBfu4+b/QcgU+Ujk9bo30NMwmPcuDHKAWaqK6CvV3fbXYaifay6nqTaT XGeM13iNtQA= =HABK -----END PGP SIGNATURE----- --=-=-=--