Re: Development schedule

Поиск
Список
Период
Сортировка
От Andrew Dunstan
Тема Re: Development schedule
Дата
Msg-id 2132.24.211.165.134.1109423588.squirrel@www.dunslane.net
обсуждение исходный текст
Ответ на Re: Development schedule  (Bruce Momjian <pgman@candle.pha.pa.us>)
Ответы Re: Development schedule  ("Joshua D. Drake" <jd@commandprompt.com>)
Список pgsql-hackers
Bruce Momjian said:
> Tom Lane wrote:
>> Bruce Momjian <pgman@candle.pha.pa.us> writes:
>> > Tom Lane wrote:
>> >> If this were an ordinary devel cycle then I'd be fine with it
>> >> running a year, but I think we really do need to plan for a shorter
>> >> than normal cycle so we can clean up 8.0 kinks in a reasonably
>> >> timely fashion.
>>
>> > Let's see how much 8.0 cleanup we need.  At this point I haven't
>> > seen any major things needing cleanup.
>>
>> However, people are asking us for a schedule target now; "wait and
>> see" isn't the answer they need.  My feeling is that we should bet on
>> there being some issues, rather than bet on there not being any.
>
> Uh, they want to know now?

YES! Yes yes yes! I try to plan my time, and the feature freeze data is very
important in that planning.

Also, regardless of the issues Tom raised, 18 months is too long a release
cycle, IMNSHO. If you do that and you take the time from feature freeze of
release n to release date of release n+1, a developer could wait 2 years
from the date of submission to see his/her feature in a release. 2 years is
an eternity in this game. Just my $0.02 worth.

cheers

andrew




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

Предыдущее
От: Neil Conway
Дата:
Сообщение: Re: idea for concurrent seqscans
Следующее
От: "Joshua D. Drake"
Дата:
Сообщение: Re: Development schedule