Re: 8.4 release planning

Поиск
Список
Период
Сортировка
От Jonah H. Harris
Тема Re: 8.4 release planning
Дата
Msg-id 36e682920901260844n2b11cd53oebafaca0faddd146@mail.gmail.com
обсуждение исходный текст
Ответ на Re: 8.4 release planning  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: 8.4 release planning  (Christopher Browne <cbbrowne@gmail.com>)
Список pgsql-hackers
On Mon, Jan 26, 2009 at 11:33 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> That would depend on timing then.  Trying to get people to upgrade to 8.4 is
> going to be difficult if they're waiting on Hot Standby, which means less
> in-the-field testing of the 8.4 code base until the 8.5 release.

[ deja vu... ]  Just like no one was going to bother upgrading to 8.3
because what they wanted wouldn't be there till 8.4, and the similar
claims we heard about 8.2 and 8.1 before that ...

I'm not trying to be an alarmist, I'm just stating what I saw when I was @ EDB.  Customers, especially those with large databases or small admin teams, would definitely wait for features before upgrading.  Some people waited specifically for HOT or features that would benefit them specifically.  My only gripe with a small window between 8.4 and 8.5 was just that I believe people would be more likely to wait until 8.5 rather than upgrading twice in the same year.  Though, as I generally like people to be using the latest version of PG, I'd certainly be happy to be wrong on this.
 
> Similarly,
> if we're looking at a quick 8.5 around September/October (having no commit
> fests), that means it will probably be early 2011 for 8.6, which is fairly
> unacceptable for the other patches currently in the queue.

Right, one of the major considerations here is allowing other
development to get started again (and not be looking at two years wait
to see the light of day).

Agreed.

--
Jonah H. Harris, Senior DBA
myYearbook.com

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Merlin Moncure
Дата:
Сообщение: Re: 8.4 release planning
Следующее
От: "Kevin Grittner"
Дата:
Сообщение: Re: More FOR UPDATE/FOR SHARE problems