| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL 10 kick-off |
| Date: | 2016-08-01 15:54:11 |
| Message-ID: | CANP8+jKGv7uQ+w5hAZnKku1A7yRo4Xur=0mQq_tNfpDGAmycaw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1 August 2016 at 16:25, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> - The next major release of PostgreSQL (after 9.6) will be known as
> PostgreSQL 10. (The actual version number of the first production
> release will as before have a minor version number of .0, so the actual
> release number will be 10.0.) Again, this jump does not change any
> policies or conventions on backward compatibility.
My understanding is that for 10.0 we will have this define
#define PG_VERSION_NUM 100000
and for 10.1, which is the first maintenance release this will change to
#define PG_VERSION_NUM 100001
effectively allowing many future versions.
Can we confirm/refute these details now to make sure we are all in tune?
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-08-01 16:04:45 | Re: PostgreSQL 10 kick-off |
| Previous Message | Tom Lane | 2016-08-01 15:49:41 | New version numbering practices |