I remember James Gosling once talking about all of the people who would come up to him complaining about problems they were having with Java 1.4.2, and he'd just look at them and ask them why they didn't just move to Java 5 where the problems were fixed. At JavaOne 2015, Georges Saab, Oracle VP of Software Development, had similar advice to those experiencing development pains with earlier versions of the release, although he couched his terms in a slightly more gentle manner than Gosling may have.
"We're cleaning out the release machinery and getting everyone used to moving the platform forward," said Saad, admitting that some of the laziness we see from organizations wanting to remain on older platforms is born out of the long release cycle that existed between versions 6 and 7 of the JDK. Basically, organizations got complacent, and regularly updating their JDK platform fell off the radar. Now it's turning into a bit of a pain getting organizations back into the habit.
"We're cleaning out the release machinery and getting everyone used to moving the platform forward."
Georges Saab, Oracle VP of Software Development
And it's not just about full version releases, but staying on top of incremental releases is important as well. Incremental releases not only fill in security holes and fix bugs, but they also provide performance improvements and feature enhancements.
For more insights on what Saad had to say at JavaOne 2015, take a look at the following article: