llvm.org GIT mirror llvm / b742ff0
updates to make it clear that this applies to clang and other llvm subprojects. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@112781 91177308-0d34-0410-b5e6-96231b3b80d8 Chris Lattner 8 years ago
1 changed file(s) with 24 addition(s) and 11 deletion(s). Raw diff Collapse all Expand all
4242 is to eliminate miscommunication, rework, and confusion that might arise from
4343 the distributed nature of LLVM's development. By stating the policy in clear
4444 terms, we hope each developer can know ahead of time what to expect when
45 making LLVM contributions.

45 making LLVM contributions. This policy covers all llvm.org subprojects,
46 including Clang, LLDB, etc.

4647

This policy is also designed to accomplish the following objectives:

4748
4849
7677
7778
7879
79

Developers should stay informed by reading at least the

80 llvmdev email
81 list. If you are doing anything more than just casual work on LLVM, it is
82 suggested that you also subscribe to the
83 llvm-commits
84 list and pay attention to changes being made by others.

80

Developers should stay informed by reading at least the "dev" mailing list

81 for the projects you are interested in, such as
82 llvmdev for
83 LLVM, cfe-dev
84 for Clang, or
85 href="http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev">lldb-dev
86 for LLDB. If you are doing anything more than just casual work on LLVM, it
87 is suggested that you also subscribe to the "commits" mailing list for the
88 subproject you're interested in, such as
89 llvm-commits,
90 cfe-commits,
91 or lldb-commits.
92 Reading the "commits" list and paying attention to changes being made by
93 others is a good way to see what other people are interested in and watching
94 the flow of the project as a whole.

8595
8696

We recommend that active developers register an email account with

8797 LLVM Bugzilla and preferably subscribe to
8898 the llvm-bugs
89 email list to keep track of bugs and enhancements occurring in LLVM.

99 email list to keep track of bugs and enhancements occurring in LLVM. We
100 really appreciate people who are proactive at catching incoming bugs in their
101 components and dealing with them promptly.

90102
91103
92104
233245 them short.
234246
235247
236

Note that llvm/test is designed for regression and small feature tests

237 only. More extensive test cases (e.g., entire applications, benchmarks, etc)
248

Note that llvm/test and clang/test are designed for regression and small

249 feature tests only. More extensive test cases (e.g., entire applications,
250 benchmarks, etc)
238251 should be added to the llvm-test test suite. The llvm-test suite is
239252 for coverage (correctness, performance, etc) testing, not feature or
240253 regression testing.

257270 testcase so we know if the fix/feature ever regresses in the
258271 future.
259272
260
  • Code must pass the dejagnu (llvm/test) test suite.
  • 273
  • Code must pass the llvm/test test suite.
  • 261274
    262275
  • The code must not cause regressions on a reasonable subset of llvm-test,
  • 263276 where "reasonable" depends on the contributor's judgement and the scope of