Skip site navigation (1) Skip section navigation (2)

Re: 8.5 development schedule

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, jd(at)commandprompt(dot)com, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: 8.5 development schedule
Date: 2009-07-01 17:39:46
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Kevin Grittner wrote:
> Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com> wrote: 
> > I could imagine an enterprise plan that says "we'll upgrade to
> > the current production release in January [after christmas sales]";
> > or "we'll begin to upgrade the January after [feature-x] is in
> > production".
> > 
> > But in neither case does it help my long term planning to know if
> > the current version January release is scheduled to be called 8.4
> > or 8.5 or 9.1 (which is really all that the current system helps
> > me predict).
> It would help with that if you didn't plan on features which had not
> been committed, and the release date didn't slip.  It's been a little
> embarrassing at times to have told people not to try to mitigate
> performance problems on the application side because I've confirmed
> that the semijoin / antijoin code already committed to the 8.4 release
> solves the problem, and the release was expected around the start of
> the year.

Where did you see 8.4 was scheduled to be released around the start of
the year?  I never never seen that and would have disputed anyone saying
it publicly.

  Bruce Momjian  <bruce(at)momjian(dot)us>

  + If your life is a hard drive, Christ can be your backup. +

In response to


pgsql-hackers by date

Next:From: Joshua D. DrakeDate: 2009-07-01 17:43:43
Subject: Re: 8.5 development schedule
Previous:From: Tom LaneDate: 2009-07-01 17:39:30
Subject: Re: 8.5 development schedule

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group