Re: Can't see my Issue

From: Michel Feinstein <michelfeinstein(at)gmail(dot)com>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: "pgadmin-support lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org>
Subject: Re: Can't see my Issue
Date: 2019-05-29 14:49:28
Message-ID: CAEg4jbMbDg2fkP0yY4Q=mbZ6E3TRP_v=y_6ZjWPtif31byo+1w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Ok, thanks for the clarification.

On Wed, May 29, 2019, 11:46 Dave Page <dpage(at)pgadmin(dot)org> wrote:

>
>
> On Wed, May 29, 2019 at 5:57 AM Michel Feinstein <
> michelfeinstein(at)gmail(dot)com> wrote:
>
>> Hi,
>>
>> In a previous email I suggested the use of a master password. Now I can
>> see at the pgAdmin 4.7 release notes that it was shipped, so I went to the
>> issue page (#4184), but I can't find it in the issue list, and I get a 403
>> error on the issue's link.
>>
>
> It's currently hidden and will be unlocked sometime after release.
>
>
>>
>> I wanted to see the implementation and since it wasn't attributed to me
>> at the release notes or my user at Redmine, as the releases usually are,
>> does it means I am blocked from it?
>>
>
> We don't typically attribute features to people other than the author of
> the code, unless there was non-trivial work done to try to track down an
> issue or similar, for example, someone writing a complex test case or proof
> of concept.
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>

In response to

Browse pgadmin-support by date

  From Date Subject
Next Message Akshay Joshi 2019-05-30 12:25:21 pgAdmin 4 v4.7 released
Previous Message Dave Page 2019-05-29 14:46:10 Re: Can't see my Issue