On 06/20/2018 10:06 AM, Willy Tarreau wrote:
On Wed, Jun 20, 2018 at 09:47:25AM +0200, Frederic Lecaille wrote:
Here is a few more reg testing files with a special one for Olivier (see
Merged, thanks Fred.
I think we should start to think about using a new tag for patches about
regtests. We already use "TESTS" from time to time for the tests directory
but it contains a bit of whatever. Maybe something short like "REGTEST"
could be easy to spot in logs ? Or feel free to suggest and use anything
else that you see fit.
Ok why not REGTEST (=> new patch for CONTRIBUTING).
>From ac705a3bcc91fcd02e4cc4497f32e9d1641d5c27 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20L=C3=A9caille?= <flecai...@haproxy.com>
Date: Wed, 20 Jun 2018 10:14:01 +0200
Subject: [PATCH] DOC: Add new REGTEST tag info about reg testing.
CONTRIBUTING | 3 +++
1 file changed, 3 insertions(+)
diff --git a/CONTRIBUTING b/CONTRIBUTING
index 9e0d625..b5ba182 100644
@@ -566,6 +566,9 @@ patch types include :
- LICENSE licensing updates (may impact distro packagers).
+ - REGTEST updates to any of the regression testing files found in reg-tests
+ directory, including README or any documentation file.
When the patch cannot be categorized, it's best not to put any type tag, and to
only use a risk or complexity information only as below. This is commonly the