Difference between revisions of "Checklist/XenHypervisorReleaseWithMarketing"

From Xen
(Press Release)
(Press Release)
Line 47: Line 47:
 
** '''Important note:''' the earlier of the dates above are a point of no return. The release '''must''' happen at this date
 
** '''Important note:''' the earlier of the dates above are a point of no return. The release '''must''' happen at this date
 
** Agree a live '''date and time''' : this is the time when
 
** Agree a live '''date and time''' : this is the time when
  +
*** All '''Documentation''' must be live
  +
*** All pages listed in '''Publishing the release on the XenProject website''' must be live (note that Joomla has a scheduling mechanism : in other words you can create artefacts and objects and they stay hidden ). Some artefacts such as *Hypervisor Downloads* module can be done within an hour ow two after the date
   
 
== Documentation ==
 
== Documentation ==

Revision as of 10:34, 31 January 2014

Icon Info.png This list contains a complete checklist for making a Xen Release, including PR


Planning the Release

  • Agree a rough schedule of RC's
  • Plan and communicate a schedule of Checklist/Kicking_off_Test_Days
  • Start establishing the list of features on publicity@lists.xenproject.org
  • Reach out to Sarah Conway <sconway@linuxfoundation.org> to get started on the press release (takes about 4 weeks). Ideally Sarah ought to be contacted before we make the first RC

Making the Release

Step 1: See Checklist/XenHypervisorRelease

Step 2: Branch the codebase

Step 3: Publish source tarballs
Pictogram voting comment 15px.png Action Ian Jackson: Add instructions; Ian Jackson normally creates these

Publishing the release on the XenProject website

Step 4: Publish the tarballs on http://xenproject.org/downloads/xen-archives.html - this requires website admin rights and is done in the Docman component. Notes:

Step 5: Update the *Hypervisor Downloads* module to include a link to the latest release. Remove older ones as appropriate

Step 6: Announce on all developer mailing lists, user lists and the announce lists. Important note: these announcements must happen *after* the press release has gone out on the wire and the timing must be *coordinated* with the press team. Otherwise the release will not make a media impact.

Step 7: Publish blog post

Press Release

Step 1: Preparation and Approval

  • About 2-3 weeks before the press release, a draft of the press release should be available. Ping Sarah Conway <sconway@linuxfoundation.org>
  • The press release needs to be reviewed (by somebody who has a little experience)
  • The press release needs to be approved by the Advisory Board. Sarah can drive this.

Step 2: Scheduling

  • Before the release, agree a date with Sarah Conway <sconway@linuxfoundation.org> on when
    • The press release gets sent out to the wire
    • When journalists are pre-briefed
    • Important note: the earlier of the dates above are a point of no return. The release must happen at this date
    • Agree a live date and time : this is the time when
      • All Documentation must be live
      • All pages listed in Publishing the release on the XenProject website must be live (note that Joomla has a scheduling mechanism : in other words you can create artefacts and objects and they stay hidden ). Some artefacts such as *Hypervisor Downloads* module can be done within an hour ow two after the date

Documentation