Re: Bug when a column is JSON?

Dave,

Sorry about the typo in the previous missive, it *should* have read;

We've just gotten the 4.*10* release in .deb format. Will we have to wait
until 4.*12* or maybe 4.*14* until we will see 4.*11*?

Otherwise, what platforms *does* the pgAdmin developers release on?

Since it isn't apparently *all* of the platforms that pgAdmin4 is developed
for, shouldn't the pgAdmin4 developers do so? If not, shouldn't the triage
be better, and the rapid release be slower? As you are aware, there have
been several instances where a new version has *broken* important
functionality in pgAdmin4. It doesn't do a large portion of the user base
any favors if the developers release a *fix* in the form of a new version a
couple of days latter only to leave entire platforms bereft of that
solution.

rik.

On Thu, Jul 25, 2019 at 8:14 AM Dave Page <dpage(at)pgadmin(dot)org> wrote:

>
>
> On Thu, Jul 25, 2019 at 1:11 PM richard coleman <
> rcoleman(dot)ascentgl(at)gmail(dot)com> wrote:
>
>> Fahar,
>>
>> We've *just* gotten the 4.*10* release in .deb format. Will we have to
>> wait until 4.*11* or maybe 4.*13* until we will see 4.10?
>>
>
> Neither Fahar nor the rest of the pgAdmin developers have any part in the
> production of the Debian packages. That is handled by a separate team who
> produce all the Debian/Ubuntu packages on apt.postgresql.org.
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>