[doc] added documentation for pre-merge testing
Differential Revision: https://reviews.llvm.org/D100936
kuhnel on Wed, Apr 21, 2:33 AM.Authored by
Added @goncharov as he's working on pre-merge testing.
Hi @jerryct ,
Yes you are right, things are not as clear as they should be. I guess the main reason is that the documentation does not always reflect the reality of the project. I have an improvement of the documentation as open issue. In an ideal world we would have a "test strategy" document, that would explain all of this.
Let me give you my high-level picture (not sure if everyone agrees with that):
I did not add pre-mege testing to the developer policy, as it's not (yet) an agreed services within the community.
Does that answer your questions?
Maybe it would be helpful to add one sentence which explicitly states that pre-merge is optional and one need to opt-in with what is described in "Requirements". Maybe in the chapter "Requirements".