xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>,
	xen-announce@lists.xenproject.org,
	xen-devel@lists.xenproject.org, xen-users@lists.xenproject.org
Cc: security-team-members@xenproject.org
Subject: Re: Vulnerability embargo dates - add your public holidays
Date: Wed, 10 May 2017 15:51:51 +0200	[thread overview]
Message-ID: <3fc25078-067c-0ffc-12c2-88b113cd751f@suse.com> (raw)
In-Reply-To: <22803.6113.486674.72765@mariner.uk.xensource.com>

On 10/05/17 15:38, Ian Jackson wrote:
> When the Xen Project Security Team talks to discoverers about choice
> of release dates for security vulnerabilities, we generally try to
> avoid known public holidays (subject to other constraints such as the
> discoverer's requirements, the Xen Project policy, and so on).
> 
> We wish to make this arrangement a bit more formal, and in particular
> to provide discoverers (who ultimately decide disclosure dates) and
> the Security Team (who often give advice) with good information to
> support their decisions.
> 
> To this end we have created a wiki page where interested community
> members can document public holidays which would affect their ability
> to respond to security issues.
> 
> Please see:
>   https://wiki.xenproject.org/wiki/HolidayCalendar

Are you planning to add a link to this page somewhere in the wiki?


Juergen

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-05-10 13:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10 13:38 Vulnerability embargo dates - add your public holidays Ian Jackson
2017-05-10 13:51 ` Juergen Gross [this message]
2017-05-10 14:07   ` Ian Jackson
2017-05-10 14:31     ` Juergen Gross
2017-05-10 14:37       ` Lars Kurth
2017-05-10 14:59         ` Lars Kurth
2017-05-10 15:56           ` Juergen Gross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3fc25078-067c-0ffc-12c2-88b113cd751f@suse.com \
    --to=jgross@suse.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=security-team-members@xenproject.org \
    --cc=xen-announce@lists.xenproject.org \
    --cc=xen-devel@lists.xenproject.org \
    --cc=xen-users@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).