summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTomek Mrugalski <tomek@isc.org>2022-01-20 11:11:40 +0000
committerTomek Mrugalski <tomek@isc.org>2022-01-24 18:58:32 +0000
commit6227b19093ccf2b1433d1b0fe2d5081f4304e212 (patch)
treee4079bdadaea65a8928f24c23bf2efa5c0db2c6e
parentb675d3a0badea8e19ffcc964b74c324ebcdcf62c (diff)
downloadisc-dhcp-6227b19093ccf2b1433d1b0fe2d5081f4304e212.tar.gz
[#221] Added note about contributing anything for client or relay
-rw-r--r--CONTRIBUTING.md8
1 files changed, 7 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 1da7b4d0..f50d5610 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -7,6 +7,12 @@ We do not require a contributors agreement. By submitting a patch or merge reque
you are agreeing that your code will be covered by the primary license for the project.
ISC DHCP is currently licensed under the MPL2.0 license.
+**NOTE**: The client (dhclient) and relay (dhcrelay) component maintenance is coming to an end.
+The 4.4.3 release is the last one that included those components and they are now considered EOL.
+The 4.5.0 release will feature server (dhcpd) only. You may still submit bugs for a client or
+relay, but those will be kept for informational purposes only. There will not be any action
+taken by ISC team on those.
+
Here's are the steps in contributing a patch:
1. **create account** on [gitlab](https://gitlab.isc.org)
@@ -193,4 +199,4 @@ Outstanding, select a small number of them and move them to whatever the current
that in mind if you plan to submit a patch and forget about it. We may accept it eventually, but
it's a much, much faster process if you participate in it.
-#### Thank you for contributing your time and expertise to the ISC DHCP Project.
+**Thank you for contributing your time and expertise to the ISC DHCP Project.**