DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Coding
  3. Java
  4. Is There Any Overlap Between Six Month Java Releases?

Is There Any Overlap Between Six Month Java Releases?

Want to learn more about the Java six-month release cycle?

Jim Connors user avatar by
Jim Connors
·
May. 06, 19 · Analysis
Like (3)
Save
Tweet
Share
8.24K Views

Join the DZone community and get the full member experience.

Join For Free

With the introduction of the new release cadence, the Java community has made good on its promise to deliver innovation at an accelerated pace. Starting with the release of JDK 9 back in September 2017, and following with JDK 10 (March 2018) and JDK 11 (September 2018), March 19, 2019 marked the general availability (GA) of JDK 12 — the fourth such six month release that has arrived, without slippage, on its expected delivery date.  For those wishing to adopt these new releases as they become available, one of the more common concerns revolves around the apparent lack of overlap between releases. That is to say, once a six-month release begins its support and update lifecycle, the previous version ends abruptly. At first glance, it appears that, in order to maintain a proper security posture, you'll have to migrate over to the latest release immediately, leaving no time for testing and certification.

There are, in fact, at least two mechanisms in place that should aid in transitioning from one six-month release to its immediate predecessor. In the description that follows, we'll discuss the ramifications of scheduling Java releases between planned quarterly security updates and, furthermore, point out that early access versions of future releases are, in general, made available well in advance of their formal release date. 

From a security perspective, built in overlap between successive releases is actually provided. The GA date for the six-month releases are deliberately placed in between planned quarterly updates (scheduled each year in January, April, July, and October). As a result, there is about a month's time where both old and new releases are at the same security baseline. If we use JDK 12 as an example, it did not receive a security update until April 16th. During that one-month period, there was no security difference between JDK 11 and JDK 12, meaning it didn't make any difference security-wise whether you were on the previous release or the one just introduced. That duration could have served as a transition and testing period where staying on JDK 11 did not sacrifice any security posture. The same overlap principle will hold true as newer JDK releases are introduced.

In the past, major Java releases were so few and far between, not to mention large and complex, that offering early access versions was a difficult and costly undertaking. The more incremental nature of the new release cadence makes it easier to provide early access versions of upcoming features and releases far in advance of their planned GA date.  For example, early access versions of JDK 13 have been available since February 2019, affording developers and testers many months of advance preparation before its planned September 2019 go-live date.

Gone are the days of three and four year Java release cycles. Granted, there are many positives to such stability, but it also left Java at an innovation disadvantage when it came to competing against other platforms for the hearts and minds of modern developers. What is, perhaps less than ideal, in this new world of rapid innovation, is the combination of having a month's worth of security baseline equivalence between old release and new, plus advance access to newer releases should assist those following the continuous integration paradigm with the new Java release cadence.

Release (agency) Java (programming language)

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • The Future of Cloud Engineering Evolves
  • Top 12 Technical Skills Every Software Tester Must Have
  • Streamlining Your Workflow With the Jenkins HTTP Request Plugin: A Guide to Replacing CURL in Scripts
  • Memory Debugging: A Deep Level of Insight

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: