Thread: Split security info into current/historic
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? -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com
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".
On 01/28/2015 10:44 AM, Magnus Hagander wrote: > > On Wed, Jan 28, 2015 at 7:20 PM, Josh Berkus <josh@agliodbs.com > <mailto: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". Is the DB move really going to happen soon enough that it doesn't make sense to split the page now? -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com
On Wed, Jan 28, 2015 at 8:39 PM, Josh Berkus <josh@agliodbs.com> wrote:
On 01/28/2015 10:44 AM, Magnus Hagander wrote:
>
> On Wed, Jan 28, 2015 at 7:20 PM, Josh Berkus <josh@agliodbs.com
> <mailto: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".
Is the DB move really going to happen soon enough that it doesn't make
sense to split the page now?
Well, splitting that page in any useful form source based is probably quite a bit of work. If that work is spent on db'ifying it, I think it's almost done already? :P
> Well, splitting that page in any useful form source based is probably > quite a bit of work. If that work is spent on db'ifying it, I think it's > almost done already? :P Splitting the static page? I think it would take me less time to do it than to discuss it. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com
On Tue, Feb 3, 2015 at 7:31 AM, Josh Berkus <josh@agliodbs.com> wrote:
> Well, splitting that page in any useful form source based is probably
> quite a bit of work. If that work is spent on db'ifying it, I think it's
> almost done already? :P
Splitting the static page? I think it would take me less time to do it
than to discuss it.
And my argument is that DBifying it would probably not be much more than that. Actually, the biggst time-sink of DBifying it is probably importing the old data..
Anyway, if it's that easy, just do it.
On 02/03/2015 06:54 AM, Magnus Hagander wrote: > On Tue, Feb 3, 2015 at 7:31 AM, Josh Berkus <josh@agliodbs.com > <mailto:josh@agliodbs.com>> wrote: > > > > Well, splitting that page in any useful form source based is probably > > quite a bit of work. If that work is spent on db'ifying it, I think it's > > almost done already? :P > > Splitting the static page? I think it would take me less time to do it > than to discuss it. > > > And my argument is that DBifying it would probably not be much more than > that. Actually, the biggst time-sink of DBifying it is probably > importing the old data.. > > Anyway, if it's that easy, just do it. After the next release, now. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com