Difference between revisions of "Checklist/XenHypervisorReleaseWithMarketing"

From Xen
(Publishing the release on the XenProject website)
(Making the Release)
Line 12: Line 12:
 
'''Step 1:''' See [[Checklist/XenHypervisorRelease]]
 
'''Step 1:''' See [[Checklist/XenHypervisorRelease]]
   
'''Step 2:''' Publish source tarballs
+
'''Step 2:''' Branch the codebase
  +
  +
'''Step 3:''' Publish source tarballs
 
{{Action|Ian Jackson}} Add instructions; Ian Jackson normally creates these
 
{{Action|Ian Jackson}} Add instructions; Ian Jackson normally creates these
   

Revision as of 10:24, 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 3: 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 4: Update the *Hypervisor Downloads* module to include a link to the latest release. Remove older ones as appropriate

Step 5: Announce on all developer mailing lists, user lists and the announce lists. Important note:

Press Release

  • About 2-3 weeks before the press release, a draft of the press release should be available. Ping Sarah Conway <sconway@linuxfoundation.org>

Documentation