On Wed, Dec 13, 2017 at 12:02 PM, Ian Jackson <[email protected]> wrote: > The 4.10 release preparation was significantly more hairy than ideal. > (We seem to have a good overall outcome despite, rather than because > of, our approach.) > > This is the second time (at least) that we have come close to failure > by committing to a release date before the exact code to be released > is known and has been made and tested. > > Evidently our docs makes it insufficiently clear not to do that. > > CC: Lars Kurth <[email protected]> > CC: Julien Grall <[email protected]> > CC: Juergen Gross <[email protected]> > Signed-off-by: Ian Jackson <[email protected]> > --- > docs/process/xen-release-management.pandoc | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/docs/process/xen-release-management.pandoc > b/docs/process/xen-release-management.pandoc > index 2ff0665..eee5dcf 100644 > --- a/docs/process/xen-release-management.pandoc > +++ b/docs/process/xen-release-management.pandoc > @@ -211,6 +211,11 @@ https://wiki.xenproject.org/wiki/Category:Xen_4.9 > Ask them to dry-run their checklist and confirm everything is OK. If not, > arrange another RC and restart this checklist. > > +7. Do not commit to a release date until > + > + * The exact xen.git commit id to be released is known. > + * That commit id has been satisfactorily tested. > +
How would you apply this directive to the particular situation we found ourselves in this time? As a reminder: * Around 3 December, we didn't think we'd be ready to release until 11 December * The security team had already set an embargo for 12 December * Our PR people advised us that 13 or 14 December would be the last suitable day to announce a release in order to have an impact before Christmas -George _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
