| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Cc: | Surinder Kumar <surinder(dot)kumar(at)enterprisedb(dot)com> |
| Subject: | Next release |
| Date: | 2017-08-24 08:58:49 |
| Message-ID: | CA+OCxoyzZpxOmd10r9msQ762HUUT3r4njS0UnEYR3PE+3xXZcg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Anyone object to doing a release on 14th September, wrapping the code on
Monday 11th? This seems like the best option for our QA folks who will be
off for EID somewhen in the two weeks before.
Assuming not, should this be 1.7 or 2.0?
If we go with 2.0, it'll be for "safety" given the proposed changes to path
management to allow both server and desktop modes to work out of the box on
Linux.
If we do that, we also need to ensure that any changes to the config
database are backwards compatible, as a 2.0 release would be a side-by-side
installation. Surinder; was it you that had looked into that?
Comments/thoughts?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim Gündüz | 2017-08-24 09:31:14 | Re: Next release |
| Previous Message | Murtuza Zabuawala | 2017-08-24 08:02:44 | [pgAdmin4][Patch]: Allow user to provide custom SSL certificates and provide .pgpass file |