From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | pgsql-www <pgsql-www(at)postgreSQL(dot)org> |
Subject: | Re: Splitting security into current/archive |
Date: | 2015-05-15 17:38:02 |
Message-ID: | 20150515173802.GD2523@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2015-05-15 20:04:30 | Re: Splitting security into current/archive |
Previous Message | Stefan Kaltenbrunner | 2015-05-15 17:37:07 | Re: Splitting security into current/archive |