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 1nSibp-0003Wf-No for pgadmin-hackers@arkaria.postgresql.org; Fri, 11 Mar 2022 16:59:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nSibo-0005wl-2A for pgadmin-hackers@arkaria.postgresql.org; Fri, 11 Mar 2022 16:59:20 +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 1nSibm-0005tw-T3 for pgadmin-hackers@lists.postgresql.org; Fri, 11 Mar 2022 16:59:19 +0000 Received: from mail-ed1-x52b.google.com ([2a00:1450:4864:20::52b]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nSibi-0007WR-Hp for pgadmin-hackers@lists.postgresql.org; Fri, 11 Mar 2022 16:59:17 +0000 Received: by mail-ed1-x52b.google.com with SMTP id g3so11696800edu.1 for ; Fri, 11 Mar 2022 08:59:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=yiak1N+uj6UDcMdn22P3LfEShit/ZWAO5pQaKRkTES8=; b=Zp2z1TqHpUQD6Nfn8T2pV4pXAhtONBfiIPMPMNQCs1ajJXw7S2q8rewumrANLvXydI S1GIhcZRyME2dI9QD//8sMfHigUQk3rluYcb8fFTG3P01sS4TSlUeev6wVlHJ2fxq8BT rh3QuvYCJSpk5Po24/QgX3js6uQM1QhijO5k77kbdFfx5bJ7QPF2AVUAGVRgDHCNyuBv uPeu/5P0iOfZqvTgDQtn+skM0TwFbHFNH11qrVwalrTJ+0mBySOCcXZd8VFUbzXiImFZ D/3pAE02t3EeKoNmZa6HxJGmRIc1GnCV0TSMwUyheFW4UlrFGhukfcCXSurcEm2u1wAu aZXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=yiak1N+uj6UDcMdn22P3LfEShit/ZWAO5pQaKRkTES8=; b=Ft05tVSKAfAfUcQ6nwiYj2Q3CdMbKAYTqJzM/0ev70NWvWWZoLe2n/G+IAA9EFxDMA PvJyUZ3veQHhqk9chABrsFJN/66i1yaoLHfd9c7kpGpXoqzLd8OUVwRUvD3P5fqfGCJO Rcp+3XaOVtgxzYDjYVNr4o07Ahzaz4gWXCuwpqdXoMyCAW0eb3qYGVbaJND1zmebr6dA gg/wJHiAMuaPSjWwPX4Zal3eTZqGHrbfANGHrTwALJ9SblC32G6ELVQ97h9z/YEqVUOA nZhRFBb3NmHU4LS+BS6WX8IsP9r/aK4EjEY7yrYAmqnqsUQgutvZkvY4aQZfnY4m7MyK aWGA== X-Gm-Message-State: AOAM532ZcGag7QqKotT0zXi0OCacO1MUZXgdr1HxKnwP+Vroo2qaySyw wWchuVMZ+YVH3l5tgqM9NX104TSR8jdLBTJtsruaiAvEJcuSCQ== X-Google-Smtp-Source: ABdhPJxToP9EER9UCnT8puMjtQ4OwEV4EjMC8Ohfe1F+s1c9qaxT7VBjCICq++aqXIrUazkDJKkknX0B9fnEh0hCrEc= X-Received: by 2002:aa7:d381:0:b0:416:293f:7de7 with SMTP id x1-20020aa7d381000000b00416293f7de7mr9877935edq.170.1647017953268; Fri, 11 Mar 2022 08:59:13 -0800 (PST) MIME-Version: 1.0 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: From: Dave Page Date: Fri, 11 Mar 2022 16:59:01 +0000 Message-ID: Subject: Re: Issue tracking To: Philippe Cloutier Cc: pgadmin-hackers@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000000b2d9105d9f44088" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000000b2d9105d9f44088 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 11 Mar 2022 at 16:29, Philippe Cloutier wrote: > Le 2022-01-19 =C3=A0 18:07, Philippe Cloutier a =C3=A9crit : > > Hi Dave, > Le 2021-11-15 =C3=A0 05:37, Dave Page a =C3=A9crit : > > > > On Fri, Nov 12, 2021 at 11:31 PM Philippe Cloutier > wrote: > >> Le 2021-11-10 =C3=A0 04:06, Dave Page a =C3=A9crit : >> >> 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 th= e > 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? > You're suggesting a general purpose project for approximately one request that we've had in many years, to resolve an issue that I've already said is on our long term todo list? The most sane way I can think of to make that happen would be to add a dedicated tracker for project infrastructure related issues (such as the buildfarm, website, GIT repo and so on), and then use that for anything that isn't directly product related. I suspect it would rarely get looked at - but I've done so anyway: https://redmine.postgresql.org/projects/pgadmin4/issues?utf8=3D=E2=9C=93&se= t_filter=3D1&sort=3Did%3Adesc&f%5B%5D=3Dtracker_id&op%5Btracker_id%5D=3D%3D= &v%5Btracker_id%5D%5B%5D=3D5&f%5B%5D=3D&c%5B%5D=3Dtracker&c%5B%5D=3Dstatus&= c%5B%5D=3Dpriority&c%5B%5D=3Dsubject&c%5B%5D=3Dassigned_to&c%5B%5D=3Dupdate= d_on&group_by=3D&t%5B%5D=3D --=20 Dave Page Blog: https://pgsnake.blogspot.com Twitter: @pgsnake EDB: https://www.enterprisedb.com --0000000000000b2d9105d9f44088 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Fri, 11 Mar 2022 at 16:29, Philipp= e Cloutier <cheal= er@gmail.com> wrote:
=20 =20 =20
Le 2022-01-19 =C3=A0 18:07, Philippe Cloutier a =C3=A9crit=C2=A0:
=20

Hi Dave,

Le 2021-11-15 =C3=A0 05:37, Dave Page a =C3=A9crit=C2=A0:
=20


On Fri, Nov 12, 2021 at 11:31 PM Philippe Cloutier <chealer@gmail.com> wrote:
Le 2021-11-10 =C3=A0 04:06, Dave Page a =C3=A9crit=C2= =A0:
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 expl= ain 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=C2=A0 is *not* just for tracking features an= d 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?

<= div>You're suggesting a general purpose project for approximately one r= equest that we've had in many years, to resolve an issue that I've = already said is on our long term todo list?

Th= e most sane way I can think of to make that happen would be to add a dedica= ted tracker for project infrastructure related issues (such as the buildfar= m, website, GIT repo and so on), and then use that for anything that isn= 9;t directly product related. I suspect it would rarely get looked at =C2= =A0- but I've done so anyway:


--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
=
EDB: https:/= /www.enterprisedb.com

--0000000000000b2d9105d9f44088--