Xen 4.16: Proposed release manager and schedule

[Ian Jackson <iwj@xxxxxxxxxxxxxx>]

We haven't formally appointed a release manager for Xen 4.16.
I was approached and asked if I would do the job, and said yes,
but I think things got stuck there.  Taking this as a prima
faciae indication of community confidence, I hereby volunteer to
take on this role.

And, I would like to tentatively propose the following schedule and
policies for Xen 4.16.  This is based on the 4.15 schedule with some
tweaks, and is intended to align the ultimate date roughly with the
4.10 and 4.13 releases, which were also in early/mid December.

I suggest we use the Lazy Consensus procedure to decide on the Release
Manager appointment, starting now (since we're already rather late).
In particular, if you feel someone else would make a better release
manager, please say so right away.

For the release schedule, assuming I'm the RM, please send comments
ASAP and in any case by noon UTC on Wednesday the 25th of August.  I
hope to finalise the schedule then.

** DRAFT **

  Friday 17th September                 Last posting date

    Patches adding new features should be posted to the mailing list
    by this cate, although perhaps not in their final version.
    (3 weeks)

  Friday 8th October                    Feature freeze
 
    Patches adding new features should be committed by this date.
    Straightforward bugfixes may continue to be accepted by
    maintainers.
    (3 weeks)

  Friday 29th October **tentatve**      Code freeze

    Bugfixes only, all changes to be approved by the Release Manager,
    on the basis of a (progressively stricter[*]) risk assessment.
    (2.5 weeks)

  Tuesday 16nd November **tentative**   Branch off staging-4.16
                                        Hard code freeze [*]

    Bugfixes for serious bugs (including regressions), and low-risk
    fixes only.  All changes to be approved by the Release Manager on
    the basis of a (progressively stricter[*]) risk assessment.

    xen-unstable open again - with caveats to avoid release disruption.

    (2.5 weeks)

  Friday 3rd December **tentative**     Final commits (docs/prep only)
  Week of 6th December **tentative**    Release
    (probably Tuesday or Wednesday)

Any patches containing substantial refactoring are to treated as
new features, even if they intent is to fix bugs.

Freeze exceptions will not be routine, but may be granted in
exceptional cases for small changes (on the basis of risk assessment,
like any release-ack).  Large series will not get exceptions.
Contributors *must not* rely on, or expect, a freeze exception, or
release schedule slip.

If as a feature proponent you feel your feature is at risk and there
is something the Xen Project could do to help, please consult me or
ask here on xen-devel.  In such situations please reach out earlier
rather than later.  I will try to put you in touch with people who may
be able to help.

[*] The distinction between Code Freeze and Hard Code Freeze is a
matter of degree, not kind; the Hard Code Freeze data and associated
tighter policy text is indicative rather than normative.

** END OF DRAFT **

Thanks,
Ian.