Re: Split security info into current/historic

Поиск
Список
Период
Сортировка
От Magnus Hagander
Тема Re: Split security info into current/historic
Дата
Msg-id CABUevExSiXEKOqYDY5pe7Q-6jmyg0r4hT_M0d5arYpxA57Auew@mail.gmail.com
обсуждение исходный текст
Ответ на Split security info into current/historic  (Josh Berkus <josh@agliodbs.com>)
Список pgsql-www

On Wed, Jan 28, 2015 at 7:20 PM, Josh Berkus <josh@agliodbs.com> wrote:
Folks,

I tried to split support/security into current and historic pages (the
later covering expired versions of postgres) ages ago and my patch was
rejected.  I can't find that now, and IIRC it was pre-Django anyway.
Can someone remind me of what the restrictions around this were, if any?

One of the things on the TODO list is to move that data into the db and generate the page, to make it easier update and less error-prone. IIRC, last time we talked about the split, we said we should do the db thing first, and then it could easily auto-split on "affects supported version". 


--

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

Предыдущее
От: Josh Berkus
Дата:
Сообщение: Split security info into current/historic
Следующее
От: Josh Berkus
Дата:
Сообщение: Re: Split security info into current/historic