Re: Heroku early upgrade is raising serious questions

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: "Jonathan S(dot) Katz" <jonathan(dot)katz(at)excoventures(dot)com>
Cc: Selena Deckelmann <selena(at)chesnok(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: Heroku early upgrade is raising serious questions
Date: 2013-04-03 04:57:01
Message-ID: 515BB69D.4030101@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

Jonathan,

> Here is a wiki I through together combining elements of both our
> current security page and thoughts from the Django one:

Thanks for getting this started! I've revised it heavily.

> One suggestion (not in the draft) is that when we do make release
> announcements containing security fixes, we do include the URL to our
> security policy to make it clear what it is.

Actually, we usually do provide a link.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message damien clochard 2013-04-03 07:55:35 Re: Heroku early upgrade is raising serious questions
Previous Message Shane Ambler 2013-04-03 01:01:36 Re: Heroku early upgrade is raising serious questions