ISC's Software Support Policy and Version Numbering
The purpose of this statement is to help users determine how long a given ISC release is likely to be supported. This information is useful when deciding when to schedule a migration, or in some cases, to help determine which version to migrate to when updating.
For the most current information on the status of any particular software version, please refer to the software status listed on the downloads page.
We have four types of major BIND 9 versions: Development, Stable, Extended Support (ESV), and Supported Preview (also known as "Subscription").
We release Development versions off of the current working (master) branch. These will be the odd-numbered major versions, starting from BIND 9.13.
There is no fixed schedule to minor Development releases; new minor versions will be made available as new features or changes become ready for field testing. Development version minor releases introduce new and updated features and may not be backward-compatible with their immediate predecessor. Development versions of BIND are suitable for those interested in experimenting with and providing feedback to ISC upon their features. There will be no alpha/beta/release candidate versions of Development versions, and it may sometimes happen that a recently-released minor version is superseded very quickly in order to address a flaw. We may not issue -P releases for Development versions with security bugs, at our discretion.
Development versions will be supported for 12 months. At the end of the 12-month period, the stabilized Development version will be re-labeled and re-released as the next Stable version, and we will begin a new Development branch.
Historically, we have recommended waiting until the third maintenance release of a new branch before deploying it in large-scale production. Beginning with BIND 9.14, we plan to publish a new Stable version annually. We will stabilize all the even-numbered major versions for production use – for example, BIND 9.14 and BIND 9.16. Each major branch will have a series of minor releases, such as BIND 9.14.0, 9.14.1, etc. Minor releases on a Stable version will include bug fixes only, to maximize stability.
Stable branches of BIND are fully supported for 12 months, but will be EOL (End of Life) as soon as the next Stable version is released, unless designated as an Extended Support version.
Extended Support versions (ESV)
Every other Stable version will be designated for Extended Support, and will be supported for at least four years from initial release. Organizations with a long internal validation, integration, or deployment cycle should consider using these versions.
Here is our current BIND 9 ESV:
- BIND 9.11 is an Extended Support version, and will be supported until December, 2021.
BIND 9.16 will be our next ESV, followed by BIND 9.20; every second Stable version after that will be ESV.
Supported Preview (also known as "Subscription," marked -S)
Releases marked with a -S are part of ISC’s Supported Preview edition. These releases provide a deployable, supported vehicle for our support customers to receive early access to new features in development. The -S edition is created for and available to support subscribers, and may also be offered to community developers for testing and feedback. The -S edition includes select unreleased software (new features and other changes) that ISC judges to be stable enough for production use. The software released in the -S versions will usually be available for experimental use via our public code repository and is intended for eventual general public release. Features in the -S version may still be in development and may be changed or even removed by the time of the public release.
The -S edition releases are actively maintained and patched in case of security vulnerabilities, just as our regular public releases are. The -S edition is offered under the same license terms as the open source BIND 9, but redistribution is constrained by the support agreement between ISC and the support subscriber.
The support plan is different from regular releases:
- When we put out a new maintenance release, we do a corresponding -S1 that will normally include all the bug fixes in the maintenance release, and will normally be a superset of the code in the corresponding maintenance version.
- If we have to do a security patch (-P), we do a corresponding -S for the -S edition. For example, if we were issuing a 9.9.8-P1, and the current release of the S edition was 9.9.8-S1, the corresponding security release for the -S edition would be numbered 9.9.8-S2.
- We add changes (new features) to the -S edition between maintenance releases that we do not add to a maintenance release of the public edition.
- We do not support more than one -S edition release on any given branch.
- When we start producing an -S edition on a new branch, we continue to support the -S edition on the prior branch for another six months to support migration.
Minimal security updates
All supported versions of BIND 9 may occasionally receive unscheduled releases in response to a critical security bug; in that case, the changes introduced between that version and its predecessor will be minimal and necessary only.
Here are our current versions and their EOL dates:
- DHCP 4.1-ESV was originally scheduled to go to EOL in December 2015, but we have extended this indefinitely to maintain a smaller-footprint edition.
- DHCP 4.4 is the current ESV version. At this point, no EOL is established.
We are nearing the end of maintenance for ISC DHCP (relative to its 20-year lifespan). The exact timeframe for EOL will depend on the maturity of Kea and other available alternatives. As we approach EOL for ISC DHCP, we may begin adding minor new features in point releases and make other exceptions to our customary support policies.
Extended Support versions (ESV)
Releases designated as ESV are ISC’s Extended Support versions. We used to incorporate the letters ESV into the version name, but we discontinued this practice after DHCP 4.1ESV.
Once the ESV designation has been assigned to a given major release we will avoid introducing any new features or functionality changes. (Exceptions may be made where the feature is of significant benefit to the user community, but in those cases, the new functionality will be enabled via a compile-time option.) However, we will install all significant and applicable bug fixes into ESVs. Each ESV will be supported for at least four years from the initial release of that major version.
With the release of Kea 1.6.0, we are changing our release model for Kea. We will have two types of major Kea versions: Development and Stable. At any given time, we should have at least two options available: one or more Stable releases and one Development release.
We release Development versions off of the current working (master) branch. These will be the odd-numbered minor versions (where the second digit of the release number is odd), starting from Kea 1.7.0, 1.7.1, 1.7.2 and so on, until that branch is replaced with the next odd-numbered minor version, Kea 1.9.0.
There is no fixed schedule to Development releases; new versions will be made available as new features or changes become ready for field testing. Maintenance releases on Development branches will introduce new and updated features and may not be backward-compatible with their immediate predecessor. Development versions of Kea are suitable for those interested in experimenting with and providing feedback to ISC, but are not recommended for production use. There will be no alpha/beta/release candidate versions of Development versions, and it may sometimes happen that a recently-released minor version is superseded very quickly in order to address a flaw. We may not issue patch releases for Development versions with security bugs, at our discretion.
Development versions will be maintained until the next Stable version is created, at which time we will begin a new Development branch (with the next odd number). We estimate Development versions will mature into Stable versions in less than a year, but this is a prediction, not a promise.
Beginning with Kea 1.6, we plan to stabilize all the even-numbered minor versions (where the second digit of the version number is even) for production use – for example, Kea 1.6 and Kea 1.8 will be Stable versions. Each of these branches will have a series of maintenance releases, such as Kea 1.6.1, 1.6.2, etc. Maintenance releases on a Stable version will include bug fixes only, to maximize stability.
Stable versions of Kea are fully supported for six months after the next Stable version is released. This means you should have ample time to migrate to a new Stable version before the older one is EOL. We do not yet have "Extended Support" versions of Kea; we still have a very high rate of new feature development and are not yet ready for a long-lived Stable branch. We expect to be able to update the Kea DHCP packages the same day we post the tarballs.
- Kea 1.3 went to EOL in December 2018.
- Kea 1.4 will be supported until August 2019 (or until we release Kea 1.6).
- Kea 1.5 will be supported until we release Kea 1.8.
- Kea 1.6 will be a Stable version, supported for six months after we release Kea 1.8 or until we release Kea 2.0, whichever is sooner.
- Kea 1.7 will be a Development version supported until we release Kea 1.9.
- Kea 1.8 will be the next Stable version after 1.6.
Other general policy guidelines
Standard support terms do not apply to Development releases, the Supported Preview edition, or alpha, beta, and Release Candidates (RCs). These are typically shorter-lived releases.