docs/process: Move MAINTAINERS update for stable to .0 release

This should be done not while branching, but right after .0 is
released.

Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
This commit is contained in:
Ian Jackson committed 2019-11-29 15:51:24 +00:00
1 parent 5731a7f7b0
commit c7d52a5be6
2 files changed
+8 -7

No files matched your search

-7
View File
@@ -84,13 +84,6 @@ Update newly diverging staging-$v according to
release-technician-checklist.txt section re README etc.,
including turning off debug.
Update new stable tree's MAINTAINERS to contain correct info for this
stable branch: usually, copy text from previous
staging-$ov:MAINTAINERS section "Stable Release Maintenance"
into new staging-$v, deleting what's there.
git cat-file blob origin/staging-$ov:MAINTAINERS >MAINTAINERS
and review the changes, commiting ONLY THE RELEVANT ONES
Set off a manual osstest run, since the osstest cr-for-branches change
will take a while to take effect:
ssh osstest.test-lab
@@ -148,5 +148,13 @@ RELEASE TARBALL
After a .0 release, update XEN_EXTRAVERSION again (to .1-pre, see above).
After a .0 release,
Update new stable tree's MAINTAINERS to contain correct info for this
stable branch: usually, copy text from previous
staging-$ov:MAINTAINERS section "Stable Release Maintenance"
into new staging-$v, deleting what's there.
git cat-file blob origin/staging-$ov:MAINTAINERS >MAINTAINERS
and review the changes, commiting ONLY THE RELEVANT ONES
Notify release manager of completion
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.