From mboxrd@z Thu Jan  1 00:00:00 1970
From: Lars Kurth <lars.kurth@xen.org>
Subject: Re: Security Response Problem Update
Date: Wed, 08 Feb 2012 17:16:30 +0000
Message-ID: <4F32ADEE.6020006@xen.org>
References: <1328719383.6133.68.camel@zakaz.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <1328719383.6133.68.camel@zakaz.uk.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

No problem: will do it tomorrow

On 08/02/2012 16:43, Ian Campbell wrote:
> Hi Lars,
>
> Please can we amend the Security Process [0] to add to the end of the
> section "5. Advisory public release:" text like:
>
>          Published advisories will be added to the Security
>          Announcements[1] wiki page.
>
> (with the link in the appropriate syntax/place)
>
> The reason is that this document also serves as our checklist for things
> to do when making a security announcement and this will serve to remind
> us to update that page.
>
> Thanks.
>
> [0] http://www.xen.org/projects/security_vulnerability_process.html
> [1] http://wiki.xen.org/wiki/Security_Announcements
>