Re: Splitting security into current/archive - Mailing list pgsql-www

From Alvaro Herrera
Subject Re: Splitting security into current/archive
Date
Msg-id 20150515173802.GD2523@alvh.no-ip.org
Whole thread Raw
In response to Re: Splitting security into current/archive  (Josh Berkus <josh@agliodbs.com>)
List pgsql-www
Josh Berkus wrote:
> On 05/13/2015 06:33 PM, Josh Berkus wrote:
> > WWW,
> > 
> > Attached is a patch which splits the security.html page into two pages:
> > security.html, which contains information about vulnerabilities in
> > supported versions, and security_archive.html, which contains
> > information about vulnerabilities which appear only in unsupported versions.
> > 
> > If the patch doesn't suit you, can you view this on github:
> > https://github.com/jberkus/pgweb/tree/split_security
> 
> Accept/reject/modify?  Anyone?

Without looking at the actual patch, your description of it does make
sense.

To me, it looks like this info should be in the web database and those
pages should be generated, not static.  That way, there's no flurry of
commits when we desupport major versions.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-www by date:

Previous
From: Stefan Kaltenbrunner
Date:
Subject: Re: Splitting security into current/archive
Next
From: Josh Berkus
Date:
Subject: Re: Splitting security into current/archive