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 X-Spam-Level: X-Spam-Status: No, score=-5.4 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9B51AC388F9 for ; Sun, 8 Nov 2020 09:01:59 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id D5C4F206E3 for ; Sun, 8 Nov 2020 09:01:58 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="FlRyrfrZ" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D5C4F206E3 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:42276 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kbgaE-0000Lh-05 for qemu-devel@archiver.kernel.org; Sun, 08 Nov 2020 04:01:58 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:37030) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kbgZS-0008K6-2o for qemu-devel@nongnu.org; Sun, 08 Nov 2020 04:01:10 -0500 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:46259) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.90_1) (envelope-from ) id 1kbgZL-000369-En for qemu-devel@nongnu.org; Sun, 08 Nov 2020 04:01:09 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1604826062; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=mieE4+4Mck1xDlU3JLj6NMm+nXxXvnb4IqVVnjEq6uw=; b=FlRyrfrZ6Cl1CrwPhwKUvD6v/oxTcGKurWdEsqfMAJaegyUDd97r2VRNP3Ug6yseMMdHyZ F+oBzKlfA1OLq6P+xej37caTRXWQ+mf2utPFlT1BGtMv24SnBcAU0ujRiJ9a0Fug2zOT+d vaMTp4z3IayXqqSt674uk5LeDTcPhSo= 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-421-kLzYLAbWOhiIG6xoA2x1Lg-1; Sun, 08 Nov 2020 04:00:58 -0500 X-MC-Unique: kLzYLAbWOhiIG6xoA2x1Lg-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 84CE1185A0D9; Sun, 8 Nov 2020 09:00:57 +0000 (UTC) Received: from thuth.remote.csb (ovpn-112-53.ams2.redhat.com [10.36.112.53]) by smtp.corp.redhat.com (Postfix) with ESMTP id 0AB6C5C1D7; Sun, 8 Nov 2020 09:00:54 +0000 (UTC) Subject: Re: Migrating to the gitlab issue tracker To: =?UTF-8?Q?Daniel_P=2e_Berrang=c3=a9?= , John Snow References: <3713093e-bf3b-bf23-a8d0-70fe429032ba@redhat.com> <3d9b264a-5e1f-b936-8455-bafc6b89ebe5@redhat.com> <20201030092324.GC99222@redhat.com> <20201030101013.GG99222@redhat.com> <37a00b98-428b-d1ca-79c2-7846ccfda651@redhat.com> <20201105155006.GP630142@redhat.com> From: Thomas Huth Message-ID: <72985bcf-668d-7472-192f-502963d2b6ad@redhat.com> Date: Sun, 8 Nov 2020 10:00:53 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <20201105155006.GP630142@redhat.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=thuth@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Received-SPF: pass client-ip=216.205.24.124; envelope-from=thuth@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/11/08 01:02:17 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Peter Maydell , =?UTF-8?Q?Alex_Benn=c3=a9e?= , Cornelia Huck , "qemu-devel@nongnu.org Developers" , Alistair Francis , =?UTF-8?Q?Philippe_Mathieu-Daud=c3=a9?= Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On 05/11/2020 16.50, Daniel P. Berrangé wrote: > On Thu, Nov 05, 2020 at 10:44:42AM -0500, John Snow wrote: >> On 11/5/20 1:14 AM, Thomas Huth wrote: >>> On 05/11/2020 01.06, John Snow wrote: >>>> On 10/30/20 6:57 AM, Peter Maydell wrote: >>>>> On Fri, 30 Oct 2020 at 10:10, Daniel P. Berrangé wrote: >>>>>> This >>>>>> makes it more appealing to leave existing bugs in the LP tracker until >>>>>> they are resolved, auto-closed, or there is a compelling reason to move >>>>>> to gitlab. >>>>> >>>>> The compelling reason is that there is no way that I want to >>>>> have to consult two entirely separate bug tracking systems >>>>> to see what our reported bugs are. We must have an entry >>>>> in the new BTS for every 'live' bug, whether it was originally >>>>> reported to LP or to gitlab. >>> [...] >>>> OK. I will try to investigate using the Launchpad API to pull our >>>> existing information, and then using the Gitlab API to re-create them. >>> >>> Before we migrate hundreds of bugs around, I think we should first check >>> which ones are stale, and which are still valid. So for all bugs that are in >>> "New" state and older than, let's say 2 years, I think we should add a >>> message a la: >>> >>> The QEMU project is currently considering to move its bug tracking to >>> another system. For this we need to know which bugs are still valid and >>> which could be closed already. Thus we are setting all older bugs to >>> "Incomplete" now. If you still think this bug report here is valid, then >>> please switch the state back to "New" within the next 60 days, otherwise >>> this report will be marked as "Expired". Thank you and sorry for the >>> inconvenience. >>> >> >> One reason to NOT do this is that if the bug does wind up being legitimate >> -- perhaps it is still a top google hit for searching a particular error >> string -- once we have migrated, there will be no recourse for the hapless >> googler. > > AFAIK, Google will index closed bugs, so they'll still appear in the > search results. > > If we really want to, we could put a comment in the bugs we're about > to close, telling people that we're using gitlab now, and to re-file > their bug there if they care about it. I'm not sure that's needed > though, since it is no different a situation to what we have already > with the 1000's of bugs we've closed over the years. > >> We can leave a generic forwarder to the new tracker once we migrate, but >> there's no way to "re-open" the issue. If someone re-files on the new >> tracker, they won't be able to update the bug to leave a new breadcrumb. >> >> However, if we migrate the bug first, we can leave breadcrumbs on the old >> tracker pointing to the new one, and then if the bug winds up being >> legitimate, googlers can follow the breadcrumb to the gitlab issue and >> either update that bug, reopen it, etc. > > IMHO they can just file a fresh bug in GitLab from scratch easily > enough by just copy+pasting the existin bug description. I don't > see a benefit in creating 100's of bugs in GitLab that we will > immediately close as being stale. I agree with Daniel. Please let's not clog the new bug tracker right from the start with hundreds of bugs - that only makes it harder to focus on the tickets that are really important. Let's use the migration instead to start as clean as possible again. Thomas