Delighted to be speaking at CFCamp 2023
(While I said "thrilled" about my previous two conference announcements, saying "delighted" here is not a downgrade. Just a desire not to sound repetitive!)
My talk will be...
(While I said "thrilled" about my previous two conference announcements, saying "delighted" here is not a downgrade. Just a desire not to sound repetitive!)
My talk will be...
Until this weekend...and it may not be noticeable to all, but I suspect some things will stand out to regular readers, starting with....
I also noticed that it marks my 17th year of blogging here, almost to the day with my first entry posted this same week back then, Apr 15 2006. That's "pretty darn interesting", as Ray Camden might say.
FWIW, I'd also blogged elsewhere--yes, on CF--prior to starting this one. And the first of those posts were in early 1998--so technically it's my 25th anniversary of blogging about CF. :-)
TLDR: The new updates are 1.8.0_371 (aka 8u371), 11.0.19, 17.0.7, and 20.0.1 respectively). For more on each of them, including what changed and the security fixes they each contain (including their CVE scores regarding urgency of concerns), see the Oracle resources I list below. Oracle calls them "critical patch updates" (yep, CPU), but they are in fact scheduled quarterly updates, so that "critical" nomenclature may sometimes be a bit overstated. And as is generally the case with these Java updates, most of them have the same changes and fixes across the versions as each other, though not always.
Note: If you use the JDK installer and may be coming to this update of Java 11 or 17 having skipped the last update, 11.0.18 or 17.0.6 respectively, please note there is an important change to the installer (for all OSs) which you should consider before proceeding. For more, see my discussion below.
For some folks, that's all they need to hear. For others, read on for topics like:
TLDR; For some folks, the above may be all you need to hear: you may be dropping your coffee and donuts now to get the update applied. Still others will see this "huge post" and think, "crap, I don't have time for this". For you, skip to the bottom and its "concluding key points". You can then decide what you think you do or don't "need to know" and pick and choose from the sections as you like.
Finally, for those who prefer because of the importance of all this to be led more carefully through understanding things (in a way that's worked for the many people I have helped so far this week, and is far more than either Adobe or Hackernews has shared), please do read on.
For more on the event, my talk, and how this means I have to skip attending/speaking at DevNexus the same week, read on.
For more, read on.
Since it's mentioned in many places on the web, I wanted to help spread this news. This cfml-slack.net URL replaces that, while the URL for the CFML Slack channel itself is unchanged: cfml.slack.com.
For more explanation/context, and especially if you may be new to considering the CFML Slack, read on.
As for CF2021, it gets updates into 2025, and the currently running pre-release of CF2023 is a great sign for the continued vitality of CF. But this looming deadline for CF2018 is a reminder that as the years roll on, we not only get new versions but we must say good-bye to old ones.
Wondering what you can do? or when CF2021 or CF2023 support will end also? And what's the difference between "core" and "extended" support Adobe sells? (The extended support plan does NOT provide updates beyond this coming July.) For more on these, including official Adobe documentation that discusses such things, as well as my thoughts on migration, costs, various options to consider, and more, do read on.
As for my session, it will be "Transitioning to Java 17 from 11 or 8 for Admins":