On 1/26/09, Tom Lane <t...@sss.pgh.pa.us> wrote: > Gregory Stark <st...@enterprisedb.com> writes: > > Put another way, the choice here is whether to have a half-baked delayed > 8.4 > > release in 6 months or a polished on-time 8.5 release in 12 months. Either > way > > the feature ships and on a not terribly different timeline either. > > > This is pretty much exactly how I see it. *Hot standby is not ready*, > and committing it into 8.4 isn't going to magically make that better. > The earliest we are going to have a HS feature that I would trust my > data to is probably ten-twelve months off. The decision we need to > make now is whether that release will be called 8.4 or 8.5; in the > former case meaning that all the stuff already in 8.4 will not reach > users' hands for close to a year more.
What about a compromise solution: release 8.4 now, then focus on wrapping up the big ticket items that didn't make it into 8.4 into a quick (as possible) 8.5 release. This means no fests. merlin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
