Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nAU3I-0002kF-8c for pgadmin-hackers@arkaria.postgresql.org; Thu, 20 Jan 2022 09:48:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nAU3H-00032h-3R for pgadmin-hackers@arkaria.postgresql.org; Thu, 20 Jan 2022 09:48:19 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nAK3c-0004U7-TW for pgadmin-hackers@lists.postgresql.org; Wed, 19 Jan 2022 23:08:01 +0000 Received: from mail-qk1-x72a.google.com ([2607:f8b0:4864:20::72a]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nAK3Z-0001M7-Sd for pgadmin-hackers@lists.postgresql.org; Wed, 19 Jan 2022 23:07:59 +0000 Received: by mail-qk1-x72a.google.com with SMTP id p9so4484536qkh.3 for ; Wed, 19 Jan 2022 15:07:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to; bh=ENpu/cRUlhvLr2KfhU4lvH58rslBqX8AVUM9OZpKsTY=; b=fid08TMvEsVQSmUSIrqYzNxpeVq+NIg//hEurOlDr+59FOt/1aV2279bZp9Ap0lvQ3 RGcTqWr17hXLWijZjQx5ruL9ef8ePNoHkY5YThcjkASIfwShhZ+YtqAgkfaMcp10oMey JuiM4O7583LUk1iZIeqVADuZnUyxq69qhhEbOxKB2xce1DCJlCC/nqqcos+9mjFHkfPc UIusbg+O2o/WEIuM5nVLmR3H9f88yCczMaN21FNDwETpWWumUJlFQxp0o8Uz49K46ZY6 ZWsOiM+Vu/QRu2nAdO4Ycq1Z1frAyk6wi+jJaUf33j4qJzF2tC8oUQWfpwbz4I4CikHs jw6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to; bh=ENpu/cRUlhvLr2KfhU4lvH58rslBqX8AVUM9OZpKsTY=; b=IuEyMJdpPRJhLzLP0155tu+GeIbB5D4xdVTDPFntMgAhcGiz22lARx92aMuSvs26sE gbtVUNOVWcW7Sx2/PIIiagzu/feau0FNxDaa0Nky0ycBot0lOOg27NhK5qSo+pkiSNcv UkyoPkUJ5OAWLTwEvwNx/Hnmi45CZk830dczrm8NRHJpbcLgebYNq7AGZHLJrOPTNjlC q+STxh6UqdT/zA7WdrihXvMyy7O/GQIiUQIdDSc5SVhCwdlUO2w+spncNktcBrHRVIiH E2xgveVXa5WfSrDjbchUr3L+Uux+l/1gZsTl7cspNo5KIgB1uEaHE7MC17eBKGdxiq1N 5r8g== X-Gm-Message-State: AOAM5301nRgvMtjmGPTQCnlnbgB5kRP13xR5QK1V/3hCkutOPWoS57Jx +crSW0m2ZsYPMl8CGiFZV12XbB8bUjA= X-Google-Smtp-Source: ABdhPJxryQkJgVj7SAb3MutrrUgp8YJJt8LHT0EXo+HR22LZ5H1Hy1uGjlSWyZbKyIx2zGWNQb+YXw== X-Received: by 2002:a37:69c2:: with SMTP id e185mr12498909qkc.141.1642633676842; Wed, 19 Jan 2022 15:07:56 -0800 (PST) Received: from [192.168.1.12] ([217.28.26.226]) by smtp.gmail.com with ESMTPSA id bp42sm500040qtb.73.2022.01.19.15.07.56 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 19 Jan 2022 15:07:56 -0800 (PST) Content-Type: multipart/alternative; boundary="------------Q3PTJNFlNcMJrb54f4EBVOHZ" Message-ID: <497591d9-e976-7ed9-301f-6ec5d3226d9e@gmail.com> Date: Wed, 19 Jan 2022 18:07:56 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: Issue tracking Content-Language: en-CA To: Dave Page Cc: pgadmin-hackers@lists.postgresql.org References: <1e895598-29e8-8c5e-775d-1dc30548fc53@gmail.com> <8a146ed4-5570-ef72-db46-9cde5a84d8b2@gmail.com> From: Philippe Cloutier In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------Q3PTJNFlNcMJrb54f4EBVOHZ Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Dave, Le 2021-11-15 à 05:37, Dave Page a écrit : > > > On Fri, Nov 12, 2021 at 11:31 PM Philippe Cloutier > wrote: > > Le 2021-11-10 à 04:06, Dave Page a écrit : >> Hi >> >> On Tue, Nov 9, 2021 at 11:23 PM Philippe Cloutier >> wrote: >> >> [...] >> >> >> The ticket I filed was set to Status "Rejected". Could >> someone either explain why or set that field to a more >> representative value? >> >> Because at the time we had no plan to change tracker. Or are you >> talking about a different ticket? > > > No, I am talking about #5042. I would obviously prefer if it had > been solved yesterday, but it does not mention any timeframe. It > is simply a report of the issue (and implicitly, a request to > solve it as soon as possible). > > Right, so it is the same ticket. We don't have any definitive plans to > change the tracker at the moment. As I mentioned, we are considering > Github, but that is by no means decided, and we may well leave things > as they are. It's also not a pgAdmin feature, which is another reason > why the issue was rejected; the issue tracker is for tracking > features/bugs in pgAdmin itself; we don't keep any infrastructure > related issues there. You are correct that this is not an issue in the pgAdmin product. However, the Redmine instance tracks issues in *projects* (as can be seen in the screenshot). If it really tracks issues in products, the instance should be adjusted accordingly. For sure, the project  is *not* just for tracking features and bugs in pgAdmin itself. There is even a tracker dedicated to support requests, so it would be hard to imagine that project issues would not be tracked when even support requests are. > >> >> >>> >>> On Wed, Nov 3, 2021 at 9:20 AM Philippe Cloutier >>> wrote: >>> >>> Greetings, >>> After starting to use pgAdmin a couple years ago and >>> struggling to track one of its issues, I figured out >>> that its issue tracker was not publicly visible (an >>> account is required to display tickets). I reported that >>> meta-issue in report #5042. >>> >>> The ticket's Status field was later set to Rejected. In >>> August, I asked in that ticket if there was a reason for >>> that. >>> >>> In September, as there had been no answer, I >>> specifically asked Dave Page, who is responsible for the >>> field's change, if he could explain it. Unfortunately, >>> more than a month later, that question remains >>> unanswered, as can be seen in the following screenshot: >>> >>> I am therefore resorting to this forum to request help >>> from the pgAdmin community. Can someone either solve >>> that or at least help elucidate? A quick look indicates >>> that Mr Page still contributes to pgAdmin. >>> >>> Thanks in advance >>> >>> -- >>> Philippe Cloutier >>> http://www.philippecloutier.com >>> >>> >>> >>> -- >>> Dave Page >>> Blog: https://pgsnake.blogspot.com >>> Twitter: @pgsnake >>> >>> EDB: https://www.enterprisedb.com >>> >> -- >> Philippe Cloutier >> http://www.philippecloutier.com >> >> >> >> -- >> Dave Page >> Blog: https://pgsnake.blogspot.com >> Twitter: @pgsnake >> >> EDB: https://www.enterprisedb.com >> > -- > Philippe Cloutier > http://www.philippecloutier.com > > > > -- > Dave Page > Blog: https://pgsnake.blogspot.com > Twitter: @pgsnake > > EDB: https://www.enterprisedb.com > -- Philippe Cloutier http://www.philippecloutier.com --------------Q3PTJNFlNcMJrb54f4EBVOHZ Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

Hi Dave,

Le 2021-11-15 à 05:37, Dave Page a écrit :


On Fri, Nov 12, 2021 at 11:31 PM Philippe Cloutier <chealer@gmail.com> wrote:
Le 2021-11-10 à 04:06, Dave Page a écrit :
Hi

On Tue, Nov 9, 2021 at 11:23 PM Philippe Cloutier <chealer@gmail.com> wrote:
[...]


The ticket I filed was set to Status "Rejected". Could someone either explain why or set that field to a more representative value?

Because at the time we had no plan to change tracker. Or are you talking about a different ticket?


No, I am talking about #5042. I would obviously prefer if it had been solved yesterday, but it does not mention any timeframe. It is simply a report of the issue (and implicitly, a request to solve it as soon as possible).

Right, so it is the same ticket. We don't have any definitive plans to change the tracker at the moment. As I mentioned, we are considering Github, but that is by no means decided, and we may well leave things as they are. It's also not a pgAdmin feature, which is another reason why the issue was rejected; the issue tracker is for tracking features/bugs in pgAdmin itself; we don't keep any infrastructure related issues there.


You are correct that this is not an issue in the pgAdmin product. However, the Redmine instance tracks issues in *projects* (as can be seen in the screenshot). If it really tracks issues in products, the instance should be adjusted accordingly.

For sure, the project  is *not* just for tracking features and bugs in pgAdmin itself. There is even a tracker dedicated to support requests, so it would be hard to imagine that project issues would not be tracked when even support requests are.


 



 



On Wed, Nov 3, 2021 at 9:20 AM Philippe Cloutier <chealer@gmail.com> wrote:

Greetings,
After starting to use pgAdmin a couple years ago and struggling to track one of its issues, I figured out that its issue tracker was not publicly visible (an account is required to display tickets). I reported that meta-issue in report #5042.

The ticket's Status field was later set to Rejected. In August, I asked in that ticket if there was a reason for that.

In September, as there had been no answer, I specifically asked Dave Page, who is responsible for the field's change, if he could explain it. Unfortunately, more than a month later, that question remains unanswered, as can be seen in the following screenshot: 

I am therefore resorting to this forum to request help from the pgAdmin community. Can someone either solve that or at least help elucidate? A quick look indicates that Mr Page still contributes to pgAdmin.

Thanks in advance

-- 
Philippe Cloutier
http://www.philippecloutier.com


--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake

EDB: https://www.enterprisedb.com

-- 
Philippe Cloutier
http://www.philippecloutier.com


--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake

EDB: https://www.enterprisedb.com

-- 
Philippe Cloutier
http://www.philippecloutier.com


--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake

EDB: https://www.enterprisedb.com

-- 
Philippe Cloutier
http://www.philippecloutier.com
--------------Q3PTJNFlNcMJrb54f4EBVOHZ--