I have a growing branch of patches to the release process docs. These
should go into tree.
As the release technican I am going to commit these (to staging, which
is the one we use for everything) unless someone clearly naks them.
If you want to improve the process, patches to these files (etc.) are
welcome but improvements should not block these documentation updates.
Ian Jackson (9):
branching checklist: drop some hg tag runes
branching checklist: Say perhaps no Config.mk changes needed
branching checklist: More detailed instructions re MAINTAINERS
release technician checklist: Reformat Config.mk changes
release technician checklist: More explicit XEN_EXTRAVERSION
docs/process: Fix minor error in formatting
docs/process: Mention .Z-pre versions
docs/process: Notify release manager, rather than editing website
docs/process: Move MAINTAINERS update for stable to .0 release
docs/process/branching-checklist.txt | 10 +---------
docs/process/release-technician-checklist.txt | 26 ++++++++++++++++++++------
2 files changed, 21 insertions(+), 15 deletions(-)
Xen-devel mailing list