[all-commits] [llvm/llvm-project] 25ba6b: [docs] Adding a Support Policy

[Renato Golin via All-commits]

  Branch: refs/heads/master
  Home:   https://github.com/llvm/llvm-project
  Commit: 25ba6b2bcd1e31d16de06eca7d42c331f9d1cf1e
      https://github.com/llvm/llvm-project/commit/25ba6b2bcd1e31d16de06eca7d42c331f9d1cf1e
  Author: Renato Golin <rengolin at systemcall.eu>
  Date:   2020-11-07 (Sat, 07 Nov 2020)

  Changed paths:
    M llvm/docs/GettingInvolved.rst
    A llvm/docs/SupportPolicy.rst

  Log Message:
  -----------
  [docs] Adding a Support Policy

As discussed in the mailing list [1-4], we need a separation of support
tiers when requiring support from the whole community versus a
sub-community. Essentially, if a sub-community is active enough and
takes maintenance into their own internal costs without affecting other
parts of the community's maintenance costs, then code that is not
immediately relevant to all parts (ie. not released, actively tested,
etc) can still find its way into the LLVM main repository without major
pain points.

The main benefit is to reduce the maintenance cost that those
sub-communities have outside of LLVM (for example, in duplicating common
code, applying the same patches on top of multiple user repositories or
downstream projects).

This document outlines the components and responsibilities of the
sub-communities with regards to maintenance costs and how they affect
the rest of the community.

It also adds an addendum on removal policies, which expand the existing
"new target removal" policy into something more generic, to encompass
any piece of code, scripts or documents in the repository.

[1] http://lists.llvm.org/pipermail/llvm-dev/2020-October/146249.html
[2] http://lists.llvm.org/pipermail/llvm-dev/2020-November/146335.html
[3] http://lists.llvm.org/pipermail/llvm-dev/2020-October/146138.html
[4] http://lists.llvm.org/pipermail/llvm-dev/2020-November/146298.html