Re: [Xen-devel] [PATCH] docs/process/xen-release-management: Lesson to learn

[Julien Grall <julien.grall@xxxxxxx>]

Hi Ian,

On 27/04/18 16:34, Ian Jackson wrote:
> Julien Grall writes ("Re: [Xen-devel] [PATCH] docs/process/xen-release-management: 
> Lesson to learn"):
> > > I guess I'm being quite selfish here.  I'm usually the release
> > > technician.  Doing release preparation at the last minute and in
> > > strange ways means lots of opportunity for me to make mistakes.
> > >
> > > I would like to put something in the release checklist that stops
> > > people putting me in a difficult position where I am (a) likely to
> > > make mistakes (b) those mistakes will be embarrassing.
> > >
> > > Putting this in the release checklist doesn't mean that it always has
> > > to be followed, of course.  Checklists are not rules; they are
> > > guidelines.
The way docs/process/xen-release-management has been written gives more 
an impression of rules/process to follow rather than guidelines. The "Do 
not commit..." seems to enforce it. It might be good to clarify that 
this is a guideline.
> > > But if this guideline is violated, and as a result I mess something up
> > > due to having to do a lot of complicated, ad-hoc, un-qa-able, work,
> > > all in a hurry, then it would be nice if it were obvious that the
> > > cause of the trouble was the decision to take this risk, rather than
> > > my carelessness or lack of attention to detail.
I think that was obvious for me :). But I understand were you are coming 
from now. And yes, I agree such guidelines would be a useful to have in 
the document.
Going forward, we probably want to find a way to minimize problem around 
XSAs coming up before the releases. This seems to happen at every 
release nowadays.
Cheers,

--
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel