Hi all,

I was reading through the project guidelines [1] and the 2.4.x STATUS file [2] and had a couple of questions about the process for test suite changes.

The guidelines say that changes to the active repository (trunk) are subject to lazy consensus, while changes to a prior branch (2.4.x) require consensus before commit. They also distinguish between ideas (RTC) and patches (CTR). In addition, the 2.4.x STATUS file has a list of RTC exceptions and tests are not mentioned there.

So my questions are:

1. Does adding or fixing/updating a test count as a patch, hence a
   committer can push it to trunk under lazy consensus?
2. Should test-only changes to 2.4.x remain under full RTC? I know that
   a bad test can mask real issues but since they don't affect runtime
   behavior I think it could have a lighter process.

Please share any thoughts on these.

Regards,
Giannis Christodoulou

[1] https://httpd.apache.org/dev/guidelines.html
[2] https://github.com/apache/httpd/blob/2.4.x/STATUS

Reply via email to