Re: Issue tracking

Поиск
Список
Период
Сортировка
От Philippe Cloutier
Тема Re: Issue tracking
Дата
Msg-id bbfb3a63-bc0c-4458-7f9c-72afdf962ff8@gmail.com
обсуждение исходный текст
Ответ на Re: Issue tracking  (Philippe Cloutier <chealer@gmail.com>)
Список pgadmin-hackers
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

В списке pgadmin-hackers по дате отправления:

Предыдущее
От: Akshay Joshi
Дата:
Сообщение: Re: [pgAdmin4][Patch]: Fixed default public IP range issue in AWS deployment
Следующее
От: Dave Page
Дата:
Сообщение: Re: Issue tracking