| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Richard Broersma Jr <rabroersma(at)yahoo(dot)com> |
| Cc: | General PostgreSQL List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Postgresql guidelines for version numbering |
| Date: | 2006-10-13 04:50:34 |
| Message-ID: | 24094.1160715034@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Richard Broersma Jr <rabroersma(at)yahoo(dot)com> writes:
> Postgresql uses three digit version number. i.e. 8.1.4
> What is warrant/constitute a change to the first digit?
There is no policy for that. Check back in the archives for the debates
that led up to renumbering 6.6 as 7.0, and later 7.5 as 8.0, and you'll
see that there wasn't a great deal of consensus about either move.
It's sort of "well, there might be enough new stuff here to represent
a sea-change in capability", but that judgement is mostly in the eye of
the beholder if you ask me.
In an alternate universe not very far away from this one, they're about
to release Postgres 6.13 ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | A. Kretschmer | 2006-10-13 04:58:44 | Re: bad error message |
| Previous Message | Patrick TJ McPhee | 2006-10-13 04:47:27 | Re: Can a function determine whether a primary key constraint exists on a table? |