Software Releases under a particular Version.

A “Version” is a series of Releases of a particular software product with a common “x.y” denomination in the first two places of the Release identifier.

A “Release,” on the other hand, is a particular image issued under a particular Version. For example, Junos 12.2R1 through Junos 12.2R8 are all Releases under the same Version 12.2, whereas Junos 12.2R1 and Junos 12.3R1 are Releases under different Versions. Releases within a particular Version generally have
common features and functionality.

The following guidelines govern EOSE and EOS for the software Releases under any particular Version (“Release EOSE” and “Release EOS”, respectively).

End of life milestone deadlines for Releases are not triggered by an EOLN. Instead, a product-specific Process Support Notification posted on Juniper’s public website at or before general availability of the first Release under the applicable software Version will specify rules for Release EOSE and Release EOS. Juniper may modify those rules from time to time by posting on its public website.

End-of-Life milestones for Releases under one Version do not affect support commitments relating to Releases for other Versions.

• Typical Timing of Release EOSE. EOSE for Releases under a particular Version generally ranges between 9 and 36 months after first general availability of the initial Release under that Version.
• Effect of Release EOSE. After Release EOSE Juniper will not be under obligation to perform any further software fixes, code changes. No further Releases will be developed or distributed for that Version.
• Typical Timing of Release EOS. Release EOS for Releases under a particular Version generally ranges between 6 and 12 months after the EOSE date for that Version.
• Effect of Release EOS. After Release EOS Juniper will not be under obligation to perform support services of any kind for any Releases under the applicable Version. Juniper will not be under any obligation to keep any such Releases available for download after Release EOS.

Subscribe to our Quarterly EOSL Updates

It’s easy to overlook or lose track of EOSL dates. Select your OEMs and receive accurate EOL and EOSL dates across multiple vendors with our quarterly EOSL email newsletter.