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

Re: 8.5 development schedule

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Ron Mayer" <rm_pg(at)cheapcomplexdevices(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <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:18:55
Message-ID: 4A4B542F02000025000281F2@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-hackers
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.
 
Ultimately, I don't know that it makes sense to plan on any
feature until its patch is accepted, so the best you can do is try to
plan on when the accepted patches will become available.  Almost by
definition, if you want a guarantee that the feature will be in some
release, the date of the release becomes unknowable in advance.
 
-Kevin

In response to

Responses

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2009-07-01 17:31:41
Subject: Re: 8.5 development schedule
Previous:From: Caleb CushingDate: 2009-07-01 17:03:19
Subject: Re: single bit integer (TINYINT) revisited for 8.5

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