public inbox for [email protected]  
help / color / mirror / Atom feed
Issue tracking
10+ messages / 2 participants
[nested] [flat]

* Issue tracking
@ 2021-11-02 22:32  Philippe Cloutier <[email protected]>
  0 siblings, 1 reply; 10+ messages in thread

From: Philippe Cloutier @ 2021-11-02 22:32 UTC (permalink / raw)
  To: [email protected]

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


Attachments:

  [image/png] bXMEZM1fWjhUYwcw.png (41.9K, 3-bXMEZM1fWjhUYwcw.png)
  download | view image

^ permalink  raw  reply  [nested|flat] 10+ messages in thread

* Re: Issue tracking
@ 2021-11-03 09:23  Dave Page <[email protected]>
  parent: Philippe Cloutier <[email protected]>
  0 siblings, 1 reply; 10+ messages in thread

From: Dave Page @ 2021-11-03 09:23 UTC (permalink / raw)
  To: Philippe Cloutier <[email protected]>; +Cc: [email protected]

Hi

Sorry, I missed that update.

The tracker is part of the PostgreSQL project infrastructure, and thus the
pgAdmin project has no control over the requirement to login to see tickets.

We are considering a move to Github issues, but that's a huge and
complex task.

On Wed, Nov 3, 2021 at 9:20 AM Philippe Cloutier <[email protected]> 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 Cloutierhttp://www.philippecloutier.com
>
>

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

EDB: https://www.enterprisedb.com


Attachments:

  [image/png] bXMEZM1fWjhUYwcw.png (41.9K, 3-bXMEZM1fWjhUYwcw.png)
  download | view image

^ permalink  raw  reply  [nested|flat] 10+ messages in thread

* Re: Issue tracking
@ 2021-11-09 23:23  Philippe Cloutier <[email protected]>
  parent: Dave Page <[email protected]>
  0 siblings, 1 reply; 10+ messages in thread

From: Philippe Cloutier @ 2021-11-09 23:23 UTC (permalink / raw)
  To: Dave Page <[email protected]>; [email protected]

Hi Dave

Le 2021-11-03 à 05:23, Dave Page a écrit :
> Hi
>
> Sorry, I missed that update.


No problem, glad to see you are still here and thank you for the reply.


>
> The tracker is part of the PostgreSQL project infrastructure, and thus 
> the pgAdmin project has no control over the requirement to login to 
> see tickets.


I know very little about the PostgreSQL project, so I cannot judge the 
control pgAdmin has over it, but for sure if pgAdmin's control is null, 
that will make solving more costly and difficult, so I tried to record 
that information in the ticket. Thanks


>
> We are considering a move to Github issues, but that's a huge and 
> complex task.


I would recommend against moving to GitHub's ITS engine, which is most 
basic.


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


>
> On Wed, Nov 3, 2021 at 9:20 AM Philippe Cloutier <[email protected]> 
> 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


Attachments:

  [image/png] bXMEZM1fWjhUYwcw.png (41.9K, 3-bXMEZM1fWjhUYwcw.png)
  download | view image

^ permalink  raw  reply  [nested|flat] 10+ messages in thread

* Re: Issue tracking
@ 2021-11-10 09:06  Dave Page <[email protected]>
  parent: Philippe Cloutier <[email protected]>
  0 siblings, 2 replies; 10+ messages in thread

From: Dave Page @ 2021-11-10 09:06 UTC (permalink / raw)
  To: Philippe Cloutier <[email protected]>; +Cc: [email protected]

Hi

On Tue, Nov 9, 2021 at 11:23 PM Philippe Cloutier <[email protected]> wrote:

>
> We are considering a move to Github issues, but that's a huge and
> complex task.
>
>
> I would recommend against moving to GitHub's ITS engine, which is most
> basic.
>
Basic is good :-). We don't actually make much use of the vast majority of
Redmine's features right now - and being able to use Github's system will
allow us to follow the workflows that most developers expect these days,
thus making it easier to allow new contributors to get started.

>
> 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?



>
>
> On Wed, Nov 3, 2021 at 9:20 AM Philippe Cloutier <[email protected]>
> 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 Cloutierhttp://www.philippecloutier.com
>>
>>
>
> --
> Dave Page
> Blog: https://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EDB: https://www.enterprisedb.com
>
> --
> Philippe Cloutierhttp://www.philippecloutier.com
>
>

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

EDB: https://www.enterprisedb.com


Attachments:

  [image/png] bXMEZM1fWjhUYwcw.png (41.9K, 3-bXMEZM1fWjhUYwcw.png)
  download | view image

^ permalink  raw  reply  [nested|flat] 10+ messages in thread

* GitHub for issue tracking (Re: Issue tracking)
@ 2021-11-12 23:13  Philippe Cloutier <[email protected]>
  parent: Dave Page <[email protected]>
  1 sibling, 0 replies; 10+ messages in thread

From: Philippe Cloutier @ 2021-11-12 23:13 UTC (permalink / raw)
  To: Dave Page <[email protected]>; [email protected]

Hi,

Le 2021-11-10 à 04:06, Dave Page a écrit :
> Hi
>
> On Tue, Nov 9, 2021 at 11:23 PM Philippe Cloutier <[email protected]> 
> wrote:
>
>>
>>     We are considering a move to Github issues, but that's a huge and
>>     complex task.
>
>
>     I would recommend against moving to GitHub's ITS engine, which is
>     most basic.
>
> Basic is good :-). We don't actually make much use of the vast 
> majority of Redmine's features right now - and being able to use 
> Github's system will allow us to follow the workflows that most 
> developers expect these days, thus making it easier to allow new 
> contributors to get started.


I'm sure using GitHub's system has advantages. All I'm saying is it's 
nowhere near mature enough to replace a Redmine tracker like pgAdmin's. 
Notice that I specified *most* basic, by which I mostly mean:

  * There is no solution tracking.
  * There is no importance tracking, or any kind of prioritization.

It is basically (pun intended) worthless for non-trivial projects.


> [...]
>
>
>>
>>     On Wed, Nov 3, 2021 at 9:20 AM Philippe Cloutier
>>     <[email protected]> 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


^ permalink  raw  reply  [nested|flat] 10+ messages in thread

* Re: Issue tracking
@ 2021-11-12 23:31  Philippe Cloutier <[email protected]>
  parent: Dave Page <[email protected]>
  1 sibling, 1 reply; 10+ messages in thread

From: Philippe Cloutier @ 2021-11-12 23:31 UTC (permalink / raw)
  To: Dave Page <[email protected]>; [email protected]

Le 2021-11-10 à 04:06, Dave Page a écrit :
> Hi
>
> On Tue, Nov 9, 2021 at 11:23 PM Philippe Cloutier <[email protected]> 
> 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).


>
>
>>
>>     On Wed, Nov 3, 2021 at 9:20 AM Philippe Cloutier
>>     <[email protected]> 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


Attachments:

  [image/png] bXMEZM1fWjhUYwcw.png (41.9K, 3-bXMEZM1fWjhUYwcw.png)
  download | view image

^ permalink  raw  reply  [nested|flat] 10+ messages in thread

* Re: Issue tracking
@ 2021-11-15 10:37  Dave Page <[email protected]>
  parent: Philippe Cloutier <[email protected]>
  0 siblings, 1 reply; 10+ messages in thread

From: Dave Page @ 2021-11-15 10:37 UTC (permalink / raw)
  To: Philippe Cloutier <[email protected]>; +Cc: [email protected]

On Fri, Nov 12, 2021 at 11:31 PM Philippe Cloutier <[email protected]>
wrote:

> Le 2021-11-10 à 04:06, Dave Page a écrit :
>
> Hi
>
> On Tue, Nov 9, 2021 at 11:23 PM Philippe Cloutier <[email protected]>
> 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.


>
>
>
>
>>
>>
>> On Wed, Nov 3, 2021 at 9:20 AM Philippe Cloutier <[email protected]>
>> 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 Cloutierhttp://www.philippecloutier.com
>>>
>>>
>>
>> --
>> Dave Page
>> Blog: https://pgsnake.blogspot.com
>> Twitter: @pgsnake
>>
>> EDB: https://www.enterprisedb.com
>>
>> --
>> Philippe Cloutierhttp://www.philippecloutier.com
>>
>>
>
> --
> Dave Page
> Blog: https://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EDB: https://www.enterprisedb.com
>
> --
> Philippe Cloutierhttp://www.philippecloutier.com
>
>

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

EDB: https://www.enterprisedb.com


Attachments:

  [image/png] bXMEZM1fWjhUYwcw.png (41.9K, 3-bXMEZM1fWjhUYwcw.png)
  download | view image

^ permalink  raw  reply  [nested|flat] 10+ messages in thread

* Re: Issue tracking
@ 2022-01-19 23:07  Philippe Cloutier <[email protected]>
  parent: Dave Page <[email protected]>
  0 siblings, 1 reply; 10+ messages in thread

From: Philippe Cloutier @ 2022-01-19 23:07 UTC (permalink / raw)
  To: Dave Page <[email protected]>; +Cc: [email protected]

Hi Dave,

Le 2021-11-15 à 05:37, Dave Page a écrit :
>
>
> On Fri, Nov 12, 2021 at 11:31 PM Philippe Cloutier <[email protected]> 
> wrote:
>
>     Le 2021-11-10 à 04:06, Dave Page a écrit :
>>     Hi
>>
>>     On Tue, Nov 9, 2021 at 11:23 PM Philippe Cloutier
>>     <[email protected]> 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
>>>         <[email protected]> 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


^ permalink  raw  reply  [nested|flat] 10+ messages in thread

* Re: Issue tracking
@ 2022-03-11 16:29  Philippe Cloutier <[email protected]>
  parent: Philippe Cloutier <[email protected]>
  0 siblings, 1 reply; 10+ messages in thread

From: Philippe Cloutier @ 2022-03-11 16:29 UTC (permalink / raw)
  To: Dave Page <[email protected]>; +Cc: [email protected]

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 
>> <[email protected]> wrote:
>>
>>     Le 2021-11-10 à 04:06, Dave Page a écrit :
>>>     Hi
>>>
>>>     On Tue, Nov 9, 2021 at 11:23 PM Philippe Cloutier
>>>     <[email protected]> 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
>>>>         <[email protected]> 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


^ permalink  raw  reply  [nested|flat] 10+ messages in thread

* Re: Issue tracking
@ 2022-03-11 16:59  Dave Page <[email protected]>
  parent: Philippe Cloutier <[email protected]>
  0 siblings, 0 replies; 10+ messages in thread

From: Dave Page @ 2022-03-11 16:59 UTC (permalink / raw)
  To: Philippe Cloutier <[email protected]>; +Cc: [email protected]

On Fri, 11 Mar 2022 at 16:29, Philippe Cloutier <[email protected]> wrote:

> 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 <[email protected]>
> wrote:
>
>> Le 2021-11-10 à 04:06, Dave Page a écrit :
>>
>> Hi
>>
>> On Tue, Nov 9, 2021 at 11:23 PM Philippe Cloutier <[email protected]>
>> 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?
>
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=✓&set_filter=1&sort=id%3Adesc...
<https://redmine.postgresql.org/projects/pgadmin4/issues?utf8=%E2%9C%93&set_filter=1&sort=id%...;

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

EDB: https://www.enterprisedb.com


^ permalink  raw  reply  [nested|flat] 10+ messages in thread


end of thread, other threads:[~2022-03-11 16:59 UTC | newest]

Thread overview: 10+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2021-11-02 22:32 Issue tracking Philippe Cloutier <[email protected]>
2021-11-03 09:23 ` Dave Page <[email protected]>
2021-11-09 23:23   ` Philippe Cloutier <[email protected]>
2021-11-10 09:06     ` Dave Page <[email protected]>
2021-11-12 23:13       ` GitHub for issue tracking (Re: Issue tracking) Philippe Cloutier <[email protected]>
2021-11-12 23:31       ` Philippe Cloutier <[email protected]>
2021-11-15 10:37         ` Dave Page <[email protected]>
2022-01-19 23:07           ` Philippe Cloutier <[email protected]>
2022-03-11 16:29             ` Philippe Cloutier <[email protected]>
2022-03-11 16:59               ` Dave Page <[email protected]>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox