Re: 8.4 release planning

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: 8.4 release planning
Дата
Msg-id 603c8f070901290519q694a1d87kcd505ca295631af1@mail.gmail.com
обсуждение исходный текст
Ответ на Re: 8.4 release planning  (Robert Treat <xzilla@users.sourceforge.net>)
Ответы Re: 8.4 release planning  (Gregory Stark <stark@enterprisedb.com>)
Список pgsql-hackers
> read up-thread, i've already shown that this would not be the case. remember,
> we reduce the pressure from the large, complex patches that bottleneck the
> process, which allows more parralell review/commit.

I read what you wrote - I just don't believe it.  My own experience is
that doing more releases is more work.  Also, two commitfests per
release means that if you can't get your patch up to snuff in two
iterations, you're bumped.  The diminished pain of being bumped will,
I think, be more than balanced out by the increased frequency of
bumps.  Many patches needed 2 or 3 commitfests to get committed; all
of the people who need 3 iterations, and anyone who needs 2 iterations
and doesn't submit until the second commitfest of the cycle, will take
two releases to get out the door.  I don't believe you're ever going
to make beta/release so low-impact that that won't be disruptive or
irritating to people.

...Robert


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

Предыдущее
От: Zdenek Kotala
Дата:
Сообщение: Re: pg_upgrade project status
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: Re: Hot standby, recovery infra