Very short overview of the Xen Project Release and Roadmap Process (for the blog). It covers the process valid up to and including Xen 4.5, and the proposal for Xen 4.6 and newer.

1. Release and Roadmap Process
Vinovyn @ Flickr

3. Master branch on xen.git
Feature Development
Code
Freeze
Point
Feature
Freeze
point
Hardening
RC’s
Release
Announcement
RELEASE-4.5.0 branch on xen.git

4. Master branch on xen.git
Feature Development
Hardening
RC’s
This is when patches for the ongoing release
need to be submitted for review
No new Features
The focus of Hardening is on Bug Fixes
No bug fixes will be accepted, unless they are
deemed a blocker

5. Release Manager:
Sends Monthly
Xen x.y Development Update
email on xen-devel@
Contributors:
Expected to reply if they are working on a feature that is not
on the list of tracked features
Expected to provide Status updates on features & bugs on the list
Not engaging with the process may lead to removal or downgrading
Release Manager:
Sends first
Xen x.y Development Update
email on xen-devel@
Deferred features from previous
release, Timetable, etc.
Contributors:
Expected to reply if they are working on a feature that is not
on the list of tracked features and tracked bugs
Same as above: can also ask for Freeze Exceptions
Release Manager:
RC Announcements, Test Days
Contributors:
Expected to provide Status updates on tracked bugs on the list
Release Manager:
Release Announcement

6. Release Manager: Wei Liu
Proposal: Tweaked Release Process for Xen 4.6
lists.xenproject.org/archives/html/xen-devel/2015-02/msg01214.html

7. Master branch on xen.git
Feature Development
Feature
Freeze
point
Wait period
to clear test pushgate
RC’s
Release
Announcement
RELEASE-4.5.0 branch on xen.git

8. Master branch on xen.git
Feature Development RC’s
This is when patches for the ongoing release
need to be submitted for review
Wait period
to clear test pushgate
No new features will be accepted, unless there is a Freeze Exception
Bug fixes are allowed, with approval by Maintainers/Release Manager
Release Manager declares that only bug fixes deemed
blockers can be accepted

9. Release Manager:
Sends Monthly
Xen x.y Development Update
email on xen-devel@
Contributors:
Expected to reply if they are working on a feature that is not
on the list of tracked features
Expected to provide Status updates on features & bugs on the list
Not engaging with the process may lead to removal or downgrading
Release Manager:
Sends first
Xen x.y Development Update
email on xen-devel@
Deferred features from previous
release, Timetable, etc.
Contributors:
Expected to reply if they are working on a feature that is not
on the list of tracked features and tracked bugs
Same as above: can also ask for Freeze Exceptions
Release Manager:
RC Announcements, Test Days
Contributors:
Expected to provide Status updates on tracked bugs on the list
Release Manager:
Release Announcement