Open Stack

Hi All,

Thinking specifically of the new upgrades chapter in the ops guide
(https://review.openstack.org/#/c/68936)...

Usually a single person takes responsibility for a change and reviewer
comments are sufficient feed back for the author to get everything in
shape.  I think the new upgrade chapter is going to take several
people fleshing out different parts before it gets to the "normally"
reviewable state.

There must be a 'usual' way to do this, but I've not worked in that
way before.  Seems most straight forward to make a review comment on
the current patch set saying who's working on what next, then post a
new patch set which someone else can claim next work on in the same
way.  The iterate until the content is complete and it builds, then
remove the "work in progress" note in the commit message and process
with normal review.

Does that make sense, will it screw up things like 'git blame' (do we
care if it does), is there some other existing convention for this?

-Jon