Oracle Visual Builder: Applications That Outlive Their First Release · Module 17 · Quarterly updates and VBCS
Reading a release note for risk
Lesson 165 of 176 · 3 min
The two categories that ACTUALLY BREAK AN APPLICATION — COMPONENT CHANGES and API CHANGES — and FINDING THEM QUICKLY. A release note is long, most of it is new features, and reading it end to end every quarter is not something anybody sustains. So read it for risk rather than for news. THE TWO CATEGORIES THAT MATTER ARE THINGS THAT CHANGE BEHAVIOUR YOU ALREADY DEPEND ON. Everything else — new components, new capabilities, new options — is optional and cannot break you by existing. COMPONENT CHANGES ARE THE FIRST, AND THE WORDS TO SEARCH FOR ARE DEPRECATED, REMOVED, CHANGED AND DEFAULT. A deprecation is a warning with a deadline — Lesson 3. A changed DEFAULT is the sneaky one: nothing in your application changed and the behaviour did, because you were relying on a value you never set. API CHANGES ARE THE SECOND, AND THE WORDS ARE ATTRIBUTE, RESOURCE, VERSION…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Visual Builder: Applications That Outlive Their First Release, with a certificate on completion and a fourteen-day refund window.