| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Mid cycle release? |
| Date: | 2006-09-14 18:16:09 |
| Message-ID: | 1302.1158257769@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
> Point I want to make is - all those are cool features(and might be
> critical for some) but I don't think they warrant a dramatic change in
> the release cycle policy ...
Any release is going to have some things that are compelling and some
that aren't, for any particular person ... it's just that those things
vary depending on who you are ...
I was heard to gripe not long ago that feature freeze during August was
bad timing. It would be interesting to try to do it during the spring
instead, just to see if people have more free time then. So for me,
+1 for a shorter-than-a-year cycle this time, independently of what
features make it or don't.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Kaltenbrunner | 2006-09-14 18:25:20 | Re: Mid cycle release? |
| Previous Message | Mark Wong | 2006-09-14 18:13:33 | Re: Lock partitions |