From owner-freebsd-ports@freebsd.org Fri May 24 11:12:35 2019 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BAB4915A7D76 for ; Fri, 24 May 2019 11:12:35 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B84D288CB2 for ; Fri, 24 May 2019 11:12:34 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mail-pg1-x533.google.com with SMTP id a3so4902427pgb.3 for ; Fri, 24 May 2019 04:12:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:reply-to:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=QlPXFNyY3Ry1NFdG47S7IfEO6573dcab90TSbnSfihs=; b=qPHpIuzhsAApE7ILZrVgsDkn8kCMEP7rN5F1CrQoNbfqgDWSjwN1w9Kn8KVSROXgAN FCA9TKE8JiGY/bPF070qo1bigVzMNRTuTA4SU+iLcA0HlmTZ4rvziDFrmZ4WieBZljy5 r21f6xUZtBMQU6kyBVpTy+KisPTPJuFI/S0+oB05TTDGPSb3Z6F1QQ0zhRcwCzhvsF9p A0qO+tes+Q5Y7PzSY+3dqo9O6XcOYrXLWGp5nb1FDlsKlkSoRIDuPMvZhSYIW9O8MYt2 CsZIrqBmsh8jagDKb3LXMNYItBP02UNx28kXBPnILjXs9YLlvu9/ufUDjHmwvXtkRErv D8vg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:reply-to:subject:to:references:from :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=QlPXFNyY3Ry1NFdG47S7IfEO6573dcab90TSbnSfihs=; b=XeG/oJynb0d7slQVm1sHKCv7JSnXWL3tZny/m9s+dvQPEmuCzpjB9i/QRqrfPLTVjL k6Z+4xtJjK+0F/2EQ7JU+iVQAmIPC/yyJcUmXxav2MAmqLRPzbzclJ89byc6wDge5WS4 SZvSyYHuV+xxyJNSw7dDS/eEcgMd0WHTcZOjf0CdudXA8rgRFr1Hw6KsfDtxsDA2RvK7 d25Ab+YvCfjl60tBSh4VBnRduGCa6M6feiVoc4hvLL2kiXpySN+8WB2+ra/GIt+REYyj c2ql6Zthebbh/cz/j12hMHBb23jd6IKg9W6bqxB4ZXiSU8Vi/uxH0JTa9Dboi+t/yU8l ZFPg== X-Gm-Message-State: APjAAAWrQVhUQ6XfYBn/GShQOVLQcP0GPhgMN+1nu6rjKfx/EGVjQKYN LlL1s+C2dnrhMWepVakV65SnUlqu X-Google-Smtp-Source: APXvYqx5XICqwc6/eWORcXRPYx70+LtccOVkUiNVR6Uks5K2AI/5X0IWqj3CLq6tmFwr4vYnXCZZMg== X-Received: by 2002:a62:4d04:: with SMTP id a4mr39859547pfb.177.1558696353358; Fri, 24 May 2019 04:12:33 -0700 (PDT) Received: from [192.168.1.105] (121-200-20-216.79c814.syd.nbn.aussiebb.net. [121.200.20.216]) by smtp.gmail.com with ESMTPSA id j2sm3904398pfb.157.2019.05.24.04.12.31 (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Fri, 24 May 2019 04:12:32 -0700 (PDT) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: Policy on closing bugs To: Grzegorz Junka , freebsd-ports@freebsd.org References: <2d6b1503-8ecd-6313-525b-e9f104fcb7f6@gjunka.com> From: Kubilay Kocak Message-ID: <3ca47a0a-e8ae-e36f-c499-b26f8997e55c@FreeBSD.org> Date: Fri, 24 May 2019 21:12:29 +1000 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:67.0) Gecko/20100101 Thunderbird/67.0 MIME-Version: 1.0 In-Reply-To: <2d6b1503-8ecd-6313-525b-e9f104fcb7f6@gjunka.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: B84D288CB2 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=qPHpIuzh; spf=pass (mx1.freebsd.org: domain of koobsfreebsd@gmail.com designates 2607:f8b0:4864:20::533 as permitted sender) smtp.mailfrom=koobsfreebsd@gmail.com X-Spamd-Result: default: False [-6.13 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[koobs@FreeBSD.org]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; FORGED_SENDER(0.30)[koobs@FreeBSD.org,koobsfreebsd@gmail.com]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FROM_NEQ_ENVFROM(0.00)[koobs@FreeBSD.org,koobsfreebsd@gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; TAGGED_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_SHORT(-0.97)[-0.970,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-ports@freebsd.org]; DMARC_NA(0.00)[FreeBSD.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[3.3.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(-2.95)[ip: (-9.10), ipnet: 2607:f8b0::/32(-3.29), asn: 15169(-2.29), country: US(-0.06)] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2019 11:12:36 -0000 On 24/05/2019 8:07 pm, Grzegorz Junka wrote: > Hey, > > Is there any policy/document when a bug can be closed? For example, is > it OK to close a bug that is fixed upstream but not yet in ports? > > Thanks > GrzegorzJ > Hi Grzegorz, Bugs are closed after they are "resolved". Resolved means a resolution has "occurred", but more precisely, the "thing reported" has been resolved. Resolved doesn't necessary mean "fixed" (see below) What resolution is appropriate/set depends on the context of the issue, usually the specific nature of the request/proposal. Is there a specific bug you're referring to? I can speak to that case specifically if so. For example however, if the bug was a "bug report for the port/package", fixed upstream hasn't fixed the port, so not usually, no, that wouldn't be considered sufficient to be "resolved" and closed. Usually commits upstream are backported to the ports, and they are closed when those are committed. There can't be policies for this perse, as its completely context/request dependent. Resolutions can take place either by way of: 1) A change is made: a commit, usually, but could be a wiki update, or a DNS update for infrastructure changes, etc. 2) One of the 'non-change' resolutions: not accepted, unable to reproduce, feedback timeout, etc Nothing about the above is special or different than most other issue trackers (generally speaking). Regarding states, we have New, Open, In Progress, Closed New: Not touched/Untriaged Open: Initially Triaged (classified) In Progress: Has a real (person) Assignee, action has started Closed: Change(s) Made, OR "Non-Change" resolution set. There's nothing special/different about these either, except that we like to have a real person assigned before in progress, and before close. Happy to answer any more questions regarding issue tracking, etc anytime -- Regards, Kubilay Bugmeister