Xen 4.15 branched; commit moratorium lifted

[Ian Jackson <iwj@xxxxxxxxxxxxxx>]

I have just branched Xen 4.15.

Patches targeted for Xen 4.15, with appropriate release-ack and
maintainer acks, should be pushed to the branch staging-4.15.

Patches targeting xen-next should be pushed to simply staging.

Please do not commit anything to the new staging which would cause it
to diverge from 4.15 in a troublesome way.  Specifically, please
avoid:

 * Anything textually intrusive - code motion, variable renaming,
   refactoring, etc.  These would make back- and forward-porting fixes
   more complicated.

 * Any change X which would make it less reasonable to use the results
   of tests of "staging" including some other changes "Y" to justify
   the goodness of the same changes Y on "staging-4.15".  This is
   relevant since the staging-4.15 branch now runs with debug off and
   we are expecting fixes to go to both trees in parallel at the
   moment.

 * Anything that needs intensive review by people working on the
   remaining outstanding issues for Xen 4.15.  Maintainers, please
   continue to prioritise any 4.15 work that is on your plate.

This regime will continue until 4.15.0 is actually released.
Hopefully fairly soon; there are only few outstanding issues.

For bugfixes targeting 4.15, you may develop them against staging
first, or you may develop them against staging-4.15 first.  In any
case we probably won't want to release 4.15 without them having been
applied to trunk.

Thanks,
Ian.