Contents

1. Oracle Announcement 1
2. Oracle Announcement 2
3. What’s the history?
4. Why was this a problem?
5. How will this be a positive change?
6. What does it mean in practice?
7. Am I happy about this change?

See announcement here.

What’s the history?

Over the past few years, we’ve seen a varied frequency of Oracle Integration Cloud (OIC) release cadence. The table below summarizes this:

Year	OIC Gen 2	OIC3
2025	3 releases (end of life) Feb25, Mar25, Apr25	3 releases (…so far…) 25.02, 25.04, 25.06
2024	4 releases Feb24, Apr24, Jun24, Aug24	5 releases 24.02, 24.04, 24.06, 24.08, 24.10
2023	8 releases Feb23, Apr23, May23, Jun23, Aug23, Oct23, Nov23, Dec23	10 releases Jan23, Feb23, Mar23, Apr23, May23, Jun23, Jul23, Aug23, 23.10, 23.12
2022	12 releases Jan22, Feb22, Mar22, Apr22, May22, Jun22, Jul22, Aug22, Sep22, Oct22, Nov22, Dec22	5 releases (NEW Product) Aug22, Sep22, Oct22, Nov22, Dec22
2021	11 releases Jan22, Feb22, Mar22, May22, Jun22, Jul22, Aug22, Sep22, Oct22, Nov22, Dec22	–
2020	12 releases Jan22, Feb22, Mar22, May22, Jun22, Jul22, Aug22, Sep22, Oct22, Nov22, Dec22	–

Why was this a problem?

A predictable release cadence is a significant step forward for Oracle integration customers who often operate large and complex end-to-end oracle cloud solutions. Per the table above, the frequency and timing of Oracle Integration updates have varied significantly over the years which makes it really challenging for organisations to anticipate and prepare for changes and regression test activity. I’ve seen this unpredictability have genuinely real-life consequences, such as delayed (or unplanned) testing cycles, rushed fixes into production and risk of service disruption in instability in live environments.

How will this be a positive change?

In committing to a more regular and predictable quarterly schedule, customers will be able to take advantage of:

• Improved Demand Planning: IT operations is a complex beast. It requires appropriately skilled personnel to be available “just in time” to handle all manor of activity. Demand planning for “change” is critical when juggling a live service and therefore improving demand planning and avoiding reactive change means that IT ops can align internal resources, testing environments and stakeholder communications around a known release calendar. The result of this will undoubtedly be reduced strain on support teams and avoids last-minute scrambles to accommodate unexpected problematic updates.
  • (I should note here. I have never really seen a catastrophic update of services like Oracle Integration. Generally they are pretty seamless… though of course it is entirely possible that an update could be incompatible with a live service implementation – e.g, if a used feature was to change or become deprecated or indeed there is a new feature that you want to take advantage of).
• Enhance Governance and Change Control: a consistent cadence supports structured change management processes. Quarterly governance checkpoints can be built into organisation’s release management frameworks so that they can build “proper” process around review, approval and implementation in a structured and controlled manner.
• Reduce Risk to Live Services: predictable release windows will enable customers to better assess the impact of new features or changes, conduct thorough regression testing and schedule fixe deployments in lower-risk periods. This maintains service continuity and user confidence.
• Align with Broader Enterprise Planning Cycles: most organisations operate quite a committed schedule of change windows. Of those organisations, many will operate a quarterly rhythm and so it’s entirely possible that the Oracle Integration releases will closely enough be synchronised with broader IT and business planning activities such as budgeting, reporting and strategic reviews.

Ultimately, this move reflects a maturing of Oracle’s cloud integration offering (much like their Oracle fusion applications release cycle).

What does it mean in practice?

This is a really simple one. A quarterly release structure means that each release is likely going to be bigger in volume of changes and new features. For the most part, this won’t interrupt current live service operation, but it will present new adoption opportunity which customers of Oracle Integration should take seriously for continuous improvement of their service.

Am I happy about this change?

YES. I know that it means fewer (but bigger) releases and that means fewer (but bigger) blog posts and condensing of my time to get new info out on this site. BUT, for the benefit of my customers operations and actually being able to answer the “When will we get OIC upgrades?” question.. this is a really positive move. I’m here for it!