docs/process/xen-release-management: Lesson to learn
authorIan Jackson <ian.jackson@eu.citrix.com>
Wed, 13 Dec 2017 11:58:00 +0000 (11:58 +0000)
committerIan Jackson <Ian.Jackson@eu.citrix.com>
Tue, 29 May 2018 09:51:02 +0000 (10:51 +0100)
commit09afb9e78e1e90ce77d5107677a8464e8410802b
tree7776ba1ff7348ab65f78cf85590d21976c993f80
parent480b5ebcc98810aa8bb670a28900a62d02a48cbc
docs/process/xen-release-management: Lesson to learn

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: Julien Grall <julien.grall@arm.com>
Acked-by: Juergen Gross <jgross@suse.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Lars Kurth <lars.kurth@citrix.com>
Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
docs/process/xen-release-management.pandoc