Re: pgAdmin III commit: Updated supported versions for 1.14. Now that we ha

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: pgAdmin III commit: Updated supported versions for 1.14. Now that we ha
Date: 2010-10-24 14:43:06
Message-ID: AANLkTin7jWv1PnPeak7s+tunrF=KUdx7V8kxJckdCY6Y@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

On Sun, Oct 24, 2010 at 2:13 PM, Guillaume Lelarge
<guillaume(at)lelarge(dot)info> wrote:
> Le 24/10/2010 01:06, Dave Page a écrit :
>> Updated supported versions for 1.14. Now that we have a PostgreSQL support policy, we can follow that for new releases of pgAdmin.
>>
>> Branch
>> ------
>> master
>>
>> Details
>> -------
>> http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=f6acdf3429dfee7ee9a2990b8fdb75d519dd50d2
>>
>> Modified Files
>> --------------
>> pgadmin/include/pgAdmin3.h |    8 ++++----
>> 1 files changed, 4 insertions(+), 4 deletions(-)
>>
>>
>
> Do we really want to do that? I mean, stopping a connection if a guy is
> not on a PostgreSQL maintained release.

It doesn't stop them, it just warns that it might explode (if memory
serves - certainly thats what happens with new releases).

In any case, unless you're willing to commit to testing every
change/new feature on 7.3, 7.4, 8.0 and 8.1, we shouldn't pretend
they're supported.

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

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2010-10-24 14:49:49 Re: 4 spaces versus tabs
Previous Message Guillaume Lelarge 2010-10-24 13:22:53 4 spaces versus tabs