All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Kurth <lars.kurth@xen.org>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Russell Pavlicek <russell.pavlicek@citrix.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	"publicity@lists.xenproject.org" <publicity@lists.xenproject.org>
Subject: Complete Checklist for making Xen Releases (including PR) - important for Xen 4.4 release
Date: Fri, 31 Jan 2014 10:58:12 +0000	[thread overview]
Message-ID: <52EB81C4.1020609@xen.org> (raw)

Hi all,

I added a checklist for making Xen Hypervisor releases as I am going to 
be on holidays (and be uncontactable - remember I tend to holiday in the 
middle of nowhere such as the Amazon) when the release is most likely made.

See 
http://wiki.xenproject.org/wiki/Checklist/XenHypervisorReleaseWithMarketing

It is important that owners for these are figured out upfront : there 
are quite a lot of small things that need doing. Also we need to give 
people access rights to our systems as needed.

Best Regards
Lars

P.S.: Please contact me with any questions *before* I leave

                 reply	other threads:[~2014-01-31 10:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=52EB81C4.1020609@xen.org \
    --to=lars.kurth@xen.org \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=publicity@lists.xenproject.org \
    --cc=russell.pavlicek@citrix.com \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.