public inbox for [email protected]
help / color / mirror / Atom feedFrom: Philippe Cloutier <[email protected]>
To: Dave Page <[email protected]>
To: [email protected]
Subject: GitHub for issue tracking (Re: Issue tracking)
Date: Fri, 12 Nov 2021 18:13:17 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+OCxoygY7SAHNrMyBw7+EngF9PqKHSLMypWJV0uqrZQfmJz8A@mail.gmail.com>
References: <[email protected]>
<CA+OCxozOPh+RjUhMzp8A9a76A+3U7N_k5srCP4JDe66u0iMBbA@mail.gmail.com>
<[email protected]>
<CA+OCxoygY7SAHNrMyBw7+EngF9PqKHSLMypWJV0uqrZQfmJz8A@mail.gmail.com>
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
view thread (10+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: GitHub for issue tracking (Re: Issue tracking)
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox