Commit Graph

12 Commits

Author SHA1 Message Date
Willy Tarreau 41f638c1eb DOC: improve the wording in CONTRIBUTING about how to document a bug fix
Insufficiently described bug fixes are still too frequent. It's a real
pain to create each new maintenance release, as 3/4 of the time is spent
trying to guess what problem a patch fixes, which is already important
in order to decide whether to pick the fix or not, but is even more
capital in order to write understandable release notes.

Christopher rightfully demands that a patch tagged "BUG" MUST ABSOLUTELY
describe the problem and why this problem is a bug. Describing the fix
is one thing but if the bug is unknown, why would there be a fix ? How
can a stable maintainer be convinced to take a fix if its author didn't
care about checking whether it was a real bug ? This patch tries to
explain a bit better what really needs to appear in the commit message
and how to describe a bug.

To be backported to all relevant stable versions.
2019-07-26 15:46:21 +02:00
Tim Duesterhus 2847f14c94 DOC: Fix typos in CONTRIBUTING
Fixes typos introduced in 09e0d7422e
as well as anything found by `spell`.
2019-06-15 21:25:06 +02:00
Willy Tarreau 09e0d7422e DOC: small updates to the CONTRIBUTING file
There's an abstract explaining what is discussed in the file, a small
explanation of how the project works, which justifies the measures
taken here, and instructions about what to do when a patch is ignored,
or how to annoy everyone.
2019-06-15 18:03:48 +02:00
Joseph Herlant e07bc14e35 DOC: Fix typos in README and CONTRIBUTING
Few typos detected by misspell in the README and CONTRIBUTING.
Even if one of them is on a listing of commits. I'm assuming that
if we want to enforce less typos in the commits, having one in the
contributing guide is not the best example.
2018-11-12 08:54:12 +01:00
Bertrand Jacquin d5e4de8e5f DOC: Fix a few typos
these are mostly spelling mistakes, some of them might be candidate for
backporting as well.
2018-10-15 19:38:15 +02:00
Frédéric Lécaille a8cf95d629 DOC: Add new REGTEST tag info about reg testing. 2018-06-20 10:20:26 +02:00
Frédéric Lécaille 4891e4055e MINOR: reg-tests: Add reg-tests/README file.
Add reg-tests/README file about how to compile and use varnishtest, and
how to produce patches to add regression testing files to HAProxy sources.

Also update CONTRIBUTING file to encourage the contributors to write
regression testing files.
2018-06-19 15:46:09 +02:00
Willy Tarreau 9d84cd602f DOC: update CONTRIBUTING regarding optional parts and message format
Make it clear that optional components must not break when disabled,
that openssl is the only officially supported library and its support
must not be broken, and that bug fixes must always be detailed.
2017-07-18 06:56:40 +02:00
Willy Tarreau 138544f4b4 DOC: update the contributing file
Bring more details, examples of good/bad messages, and avoid confusion
between commit message and message subject.
2017-03-31 16:26:46 +02:00
Tim Düsterhus 4896c440b3 DOC: Spelling fixes
[wt: this contains spelling fixes for both doc and code comments,
 should be backported, ignoring the parts which don't apply]
2016-11-29 07:29:57 +01:00
Thiago Farina 9f72a39f68 DOC: fix "needed" typo
While at it use "You" instead of "They" as in the context
it seems to make more sense to refer to "you", as it is
you that are going to be running the command, there is no
"they".

Signed-off-by: Thiago Farina <tfarina@chromium.org>
2016-04-03 14:21:22 +02:00
Willy Tarreau 11e334d972 DOC: add a CONTRIBUTING file
This file tries to explain in the most detailed way how to contribute
patches. A few parts of it were moved from the README. .gitignore was
updated.
2015-09-20 22:43:56 +02:00