Re: Sigh, we need an initdb

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Sigh, we need an initdb
Date: 2014-06-05 02:29:14
Message-ID: 27895.1401935354@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> If we are planning on keeping this rule, which it seems like at least a few
> people feel is too stringent, maybe we can consider releasing an Alpha
> version and communicate the expectation that an initdb will be required to
> go from the alpha to beta1. Then hopefully, but not certainly, no initdb
> needed once in the beta phase. Basically convert beta1 into an alpha with
> that single policy/expectation change.

I think that would just amount to adding a month of dead time in what is
already a very long beta cycle. Our past experience with releasing things
called "alphas" has been that people don't test them.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2014-06-05 06:11:19 Re: Need to backpatch 2985e16 to 9.3 and further (HS regression test out)
Previous Message David G Johnston 2014-06-05 02:13:35 Re: Sigh, we need an initdb