Create a new document under docs/process to describe our special tags. For now, only add the new backport tag.
Signed-off-by: Stefano Stabellini <[email protected]> Acked-by: Ian Jackson <[email protected]> Acked-by: Wei Liu <[email protected]> CC: [email protected] CC: [email protected] CC: [email protected] CC: [email protected] CC: [email protected] CC: [email protected] --- This is the original thread: https://marc.info/?l=xen-devel&m=157324027614941 The backport tag was agreed upon. George requested the file to be renamed to something more generic, where we could add more information later. I kept the original content and acked-by. I renamed the file to tags.pandoc. --- docs/process/tags.pandoc | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 docs/process/tags.pandoc diff --git a/docs/process/tags.pandoc b/docs/process/tags.pandoc new file mode 100644 index 0000000000..e570efdcc8 --- /dev/null +++ b/docs/process/tags.pandoc @@ -0,0 +1,23 @@ +Backport Tag +------------ + +A backport tag is an optional tag in the commit message to request a +given commit to be backported to the stable trees: + + Backport: all + +It marks a commit for being a candidate for backports to all relevant +trees. + + Backport: 4.9+ + +It marks a commit for being a candidate for backports to all stable +trees from 4.9 onward. + +Maintainers request the Backport tag to be added on commit. +Contributors are also welcome to mark their patches with the Backport +tag when they deem appropriate. Maintainers will request for it to be +removed when that is not the case. + +Please note that the Backport tag is a **request** for backport, which +will still need to be evaluated by the stable tree maintainers. -- 2.17.1
