Test suite - commit process clarifications

Giannis Christodoulou <[email protected]> Mon, 18 May 2026 12:09:16 +0200
Newsgroups	gmane.comp.apache.devel
Message-ID	<[email protected]>
This is a multi-part message in MIME format.
--------------G6xgiBxmvA2WS2vIV0IzqzFv
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

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
--------------G6xgiBxmvA2WS2vIV0IzqzFv
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    Hi all,<br>
    <br>
    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.<br>
    <br>
    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.<br>
    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.<br>
    <br>
    So my questions are:<br>
    <ol>
      <li>Does adding or fixing/updating a test count as a patch, hence
        a committer can push it to trunk under lazy consensus?</li>
      <li>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.</li>
    </ol>
    Please share any thoughts on these.<br>
    <br>
    Regards,<br>
    Giannis Christodoulou<br>
    <br>
    [1] <a class="moz-txt-link-freetext" href="https://httpd.apache.org/dev/guidelines.html">https://httpd.apache.org/dev/guidelines.html</a><br>
    [2] <a class="moz-txt-link-freetext" href="https://github.com/apache/httpd/blob/2.4.x/STATUS">https://github.com/apache/httpd/blob/2.4.x/STATUS</a>
  </body>
</html>

--------------G6xgiBxmvA2WS2vIV0IzqzFv--