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 1nT2Iz-0007We-Kq for pgadmin-hackers@arkaria.postgresql.org; Sat, 12 Mar 2022 14:01:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nT2Iy-000711-GF for pgadmin-hackers@arkaria.postgresql.org; Sat, 12 Mar 2022 14:01:12 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nSi96-0006hv-2C for pgadmin-hackers@lists.postgresql.org; Fri, 11 Mar 2022 16:29:40 +0000 Received: from mail-qt1-x830.google.com ([2607:f8b0:4864:20::830]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nSi8y-0007HT-Vv for pgadmin-hackers@lists.postgresql.org; Fri, 11 Mar 2022 16:29:39 +0000 Received: by mail-qt1-x830.google.com with SMTP id v14so3375812qta.2 for ; Fri, 11 Mar 2022 08:29:32 -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 :from:to:cc:references:in-reply-to; bh=YLQXfCO6a+CUaVWb/QCYINjUcsiBelKfjaf47uzvcJI=; b=lhB0k6YG6K4yfJW1KG7y8ka8Y6eVEC4vasZOBnuk9M7an5sHbRJETFkVdU02Qng/bD vMPncF1AmATPtp09/f0ir3BCe7LLaUrSmeJO/Z41WAckKsFc0VC4aAxNcSMO79eySta6 RkPxJ/0DV596li8dLIiH+MALjHQx2jIum0Wxq5JQK3wVxofvrgbt3ZsKdqpWSm01mlrh XSf/zNK+HDp93Ug9xlhNafqFbkb/LKjAcKpjPWxfiB3l0KnPPgZ5g2tBdPmSUf4c6mUJ E6rXoCp3a7p7UUloG7FUGVuurzfzshcXpkOuJ7C6Mpo/yA+AhymxkpkbojHnY5d4iHg7 4B7A== 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:from:to:cc:references:in-reply-to; bh=YLQXfCO6a+CUaVWb/QCYINjUcsiBelKfjaf47uzvcJI=; b=i1W4BqERXo1tE4klu9yoJdgdCEu9uKFefulIN5Is2OHy2527Hcz0ZXuQzIKOGNT5A4 v7th3eizb2ZlRVx+WK729U0IO1452qkphMlBfiWrRrLUoevWp6R+yW5t8ZrrWIC8znTw UHjjzuleaxuZln/7QuPgsMfBO0D9ivewNTgPsb9azGmY/SYdxpk7x52rFwMLXxbEH3k/ ikBMawc/oyNjupEQWj9EhoRBeaXJDLPsqNOMm8bCTu27gO23yAbeupTFUvI6nKef8kZ8 bPOk21gKRLGsWIRE13VRmyo4UwrCjAi8AgsSOUuSmHBoqAAU0kb9J2b63yCpVO9QFV1A 0gWA== X-Gm-Message-State: AOAM530AKnoO2FihDEZSYb+TsUAJqRme+MlIDYdlpfGAekjHSjBmYKNY ciyqiChPVw7IaeftuA4x5xhw5ax5xyM= X-Google-Smtp-Source: ABdhPJxDQO0Ql8+7mxi1HEvcCPf01liQu0YxoOBOUgEqSoPpMdtcjghtMboVMXwh2Q2ek0f6As0HWw== X-Received: by 2002:a05:622a:1a97:b0:2e0:62b2:4507 with SMTP id s23-20020a05622a1a9700b002e062b24507mr9027940qtc.328.1647016170904; Fri, 11 Mar 2022 08:29:30 -0800 (PST) Received: from [192.168.1.12] ([217.28.26.226]) by smtp.gmail.com with ESMTPSA id i192-20020a379fc9000000b0067b314c0ff3sm3947348qke.43.2022.03.11.08.29.30 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 11 Mar 2022 08:29:30 -0800 (PST) Content-Type: multipart/alternative; boundary="------------esUi0dT0t1Sz0Xjs0ARDBhIM" Message-ID: Date: Fri, 11 Mar 2022 11:29:29 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.2 Subject: Re: Issue tracking Content-Language: en-CA From: Philippe Cloutier To: Dave Page Cc: pgadmin-hackers@lists.postgresql.org References: <1e895598-29e8-8c5e-775d-1dc30548fc53@gmail.com> <8a146ed4-5570-ef72-db46-9cde5a84d8b2@gmail.com> <497591d9-e976-7ed9-301f-6ec5d3226d9e@gmail.com> In-Reply-To: <497591d9-e976-7ed9-301f-6ec5d3226d9e@gmail.com> 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. --------------esUi0dT0t1Sz0Xjs0ARDBhIM Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Le 2022-01-19 à 18:07, Philippe Cloutier a écrit : > > 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. > So, if we accept that the tracker's presentation is indeed wrong, presumably, if one was to ask for a general-purpose issue tracker on the Redmine instance, that request would then also be rejected? > >> >>> >>> >>>> >>>> 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 -- Philippe Cloutier http://www.philippecloutier.com --------------esUi0dT0t1Sz0Xjs0ARDBhIM Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
Le 2022-01-19 à 18:07, Philippe Cloutier a écrit :

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.


So, if we accept that the tracker's presentation is indeed wrong, presumably, if one was to ask for a general-purpose issue tracker on the Redmine instance, that request would then also be rejected?



 



 



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
-- 
Philippe Cloutier
http://www.philippecloutier.com
--------------esUi0dT0t1Sz0Xjs0ARDBhIM--