Re: A deprecation policy

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: A deprecation policy
Дата
Msg-id 12213.1234377220@sss.pgh.pa.us
обсуждение исходный текст
Ответ на A deprecation policy  (Peter Eisentraut <peter_e@gmx.net>)
Ответы Re: A deprecation policy
Список pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> I have been thinking, with a semi-formal deprecation policy, we could 
> make these decisions with more confidence.  My proposed policy goes like 
> this:

I've been thinking about this for a couple of hours, and I keep coming
back to the conclusion that if we actually enforced a policy like this
it would kill Postgres development dead.  It already takes more than a
year, on average, for a proposal to go from idea to out-in-the-field.
This policy would add another two years onto that for anything that
involved user-visible changes, which is most things.  All but the most
persistent developers are simply going to go away and not bother trying
to shepherd their ideas through such a process.

I can see the value of a more formal deprecation policy, but I think
it's gotta have a shorter time constant than this.
        regards, tom lane


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog,
Следующее
От: Teodor Sigaev
Дата:
Сообщение: Re: GIN fast insert