summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas Markwalder <tmark@isc.org>2015-03-02 13:16:36 -0500
committerThomas Markwalder <tmark@isc.org>2015-03-02 13:16:36 -0500
commitf716d04ac86b54330a103ddadc5ca72980c359ee (patch)
tree20eabeb3a892d253338b53678563da8f3ab3e86b
parenta3c8c651426758528dadc9ddd5c01e643ef80a4b (diff)
downloadisc-dhcp-f716d04ac86b54330a103ddadc5ca72980c359ee.tar.gz
[v4_2] Added EOL notice to RELNOTES
-rw-r--r--RELNOTES24
1 files changed, 24 insertions, 0 deletions
diff --git a/RELNOTES b/RELNOTES
index 1df0bf14..cde09771 100644
--- a/RELNOTES
+++ b/RELNOTES
@@ -28,6 +28,30 @@ release, which will be addressed in the future:
not both. To use both protocols simultaneously, two instances of the
relevant daemon are required, one with the '-6' command line option.
+ ------ EOL NOTICE -------
+
+Version 4.2.8 is the last regular maintenance release on the ISC DHCP 4.2 train.
+ISC will cease regular maintenance on this train at the end of March, 2015, as
+previously announced.
+
+This is an exception to our stated policy that we keep every train until two
+subsequent feature releases. We need to reduce the number of supported trains,
+and decided that keeping the 4.1.x train was important to provide options for
+applications in constrained memory environments. We have extended support
+for 4.1.x until at least December, 2015.
+
+We feel that ISC DHCP 4.3.2 provides a stable platform for most users and we
+are declaring it to be our next Extended Support Version. We plan to support
+the 4.3.x train through 2017.
+
+ISC Technical support will continue to provide commercial support for
+ISC DHCP 4.2.8 through 2015 to provide plenty of time for migration. We will
+provide back ported patches to affected customers where practical. In addition,
+we will normally also address critical security issues in recently EOLed
+versions. However, we encourage users to start planning their migration
+to 4.3.
+
+
For information on how to install, configure and run this software, as
well as how to find documentation and report bugs, please consult the
README file.