| Willy Tarreau | 5eb0917 | 2007-03-25 22:56:04 +0200 | [diff] [blame] | 1 | Special thanks to the following people for their useful contributions : |
| 2 | |
| 3 | - Aleksandar Lazic and Klaus Wagner : ability to learn application cookies. |
| 4 | - Cameron Simpson : code reviews and many cleanups. |
| 5 | - Dan Zinngrabe : Makefile for MacOS 10.4 / Darwin. |
| 6 | - Sin Yu : preliminary virtual host support and rbtree for the scheduler. |
| 7 | - Marcus Rueckert : support for username/groupname. |
| 8 | - Bryan Germann : option to exempt some sources from x-forwarded-for. |
| 9 | - Fabrice Dulaunoy : health-checks on different addresses |
| Krzysztof Piotr Oledzki | 4ad3b40 | 2008-02-04 00:00:15 +0100 | [diff] [blame] | 10 | |
| Krzysztof Piotr Oledzki | 6d45fcd | 2009-09-27 14:20:28 +0200 | [diff] [blame] | 11 | This list is quite incomplete and very outdated. For more up-to-date |
| 12 | information please look at http://haproxy.1wt.eu/contrib.html, it lists |
| 13 | not only significant code contributions (features, fixes), but also time or |
| 14 | money donations. |
| 15 | |
| Krzysztof Piotr Oledzki | 4ad3b40 | 2008-02-04 00:00:15 +0100 | [diff] [blame] | 16 | Note to contributors: it's very handy when patches comes with a properly |
| 17 | formated subject. Try to put one of the following words between brackets |
| 18 | to indicate the importance of the patch followed by a short description: |
| 19 | |
| 20 | [MINOR] minor fix, very low risk of impact |
| 21 | [MEDIUM] medium risk, may cause unexpected regressions of low importance or |
| Krzysztof Piotr Oledzki | 6d45fcd | 2009-09-27 14:20:28 +0200 | [diff] [blame] | 22 | which may quickly be discovered |
| Krzysztof Piotr Oledzki | 4ad3b40 | 2008-02-04 00:00:15 +0100 | [diff] [blame] | 23 | [MAJOR] major risk of hidden regression. This happens when I rearrange large |
| 24 | parts of code, when I play with timeouts, with variable |
| 25 | initializations, etc... |
| 26 | [BUG] fix for a minor or medium-level bug. |
| 27 | [CRITICAL] medium-term reliability or security is at risk, an upgrade is |
| 28 | absolutely required. |
| 29 | [RELEASE] release a new version |
| 30 | [BUILD] fix build issues. If you could build, no upgrade required. |
| 31 | [CLEANUP] code cleanup, silence of warnings, etc... theorically no impact |
| 32 | [TESTS] added regression testing configuration files or scripts |
| 33 | [DOC] documentation updates, no need to upgrade |
| 34 | [LICENSE] licensing updates (may impact distro packagers) |
| 35 | |
| 36 | Example: "[DOC] document options forwardfor to logasap" |