[PATCH] D26963: [docs] Add user-side for blockers/merges
Renato Golin via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Mon Dec 12 01:41:53 PST 2016
rengolin removed rL LLVM as the repository for this revision.
rengolin updated this revision to Diff 81056.
rengolin added a comment.
Addressing comments.
https://reviews.llvm.org/D26963
Files:
docs/HowToReleaseLLVM.rst
Index: docs/HowToReleaseLLVM.rst
===================================================================
--- docs/HowToReleaseLLVM.rst
+++ docs/HowToReleaseLLVM.rst
@@ -256,6 +256,23 @@
from the Meta and its priority decreased to *normal*. Debugging can continue,
but on trunk.
+To help users report regressions and propose backports, the following standard
+is followed:
+
+ #. The Meta bug is named: "[Meta] X.n Merges and Bug Fixes", where X.n is the
+ release in question.
+ #. Regressions should be linked as a blocker to that bug, as a separate entry,
+ linking both the original bug (or reporting a new one) and the meta bug.
+ When fixed on trunk, it should be backported with the approval of the code
+ owner as soon as all the tests are done and all the bots are green.
+ #. Already existing fixes proposed as backports should create new bugs entitled
+ "Merge rN to the X.n branch", where rN is the commit(s) to backport and X.n
+ is the release, which should coincide with the release in the Meta.
+
+The ultimate decision to merge / backport fixes is done by the release manager
+and the code owners, so please make sure to copy them on any correspondence
+regarding that issue.
+
Release Patch Rules
-------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D26963.81056.patch
Type: text/x-patch
Size: 1256 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20161212/e0fdc578/attachment.bin>
More information about the llvm-commits
mailing list