| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, Peter Mount <petermount(at)it(dot)maidstone(dot)gov(dot)uk>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'The Hermit Hacker'" <scrappy(at)hub(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] 6.6 release |
| Date: | 1999-12-11 02:01:09 |
| Message-ID: | Pine.LNX.4.20.9912110156400.1875-100000@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1999-12-10, Bruce Momjian mentioned:
> Maybe we just call it 7.0, and have some more incompatibility stuff in
> 7.1. Seems waiting for some .0 release is not going to work, unless we
> scrap the Feb 1 beta and just wait for all new stuff to be finished, but
> that seems worse than having a 7.1 that contains some incompatiblities.
What kind of incompatibilities are we talking about here really? Is there
anything that can't be resolved via
* big warning signs
* pg_dump or (to be created) friends
* supporting the old stuff for a while as well
* automated conversion of the things using the old stuff
* informative documents outlining the reason of the change and how to
cope with it?
Things change all the time, that's a fact of life.
If foreign keys get done this is definitely the greatest thing in the
world for the end user, so 7.0 is a good name.
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 1999-12-11 02:01:22 | Re: [HACKERS] 6.6 release |
| Previous Message | Peter Eisentraut | 1999-12-11 02:00:57 | Re: [HACKERS] 6.6 release |