Apigee Edge release process

Apigee Edge follows a continuous release model for the Public Cloud and Private Cloud versions to ensure our users can access the product innovation and enhancements quickly and at the highest quality possible.

All releases are expected to be free of interruption to Edge, unless it is a planned downtime which will be done with minimum of five business days notification. As Edge is a mission-critical infrastructure that enables access to enterprise services by developers, customers, employees and partners, new Edge releases often require our customers to perform advance planning with internal and external stakeholders. We believe a clearly communicated release cadence will assist in this planning.

Changes to Edge for Private Cloud release cycle

Based on customer feedback, Apigee has decided to move to two Apigee Edge for Private Cloud releases per year. To keep the releases evenly distributed, we will have “01” (January) and “06” (June) releases.

This change is effective immediately. Therefore, there will be no Edge for Private Cloud 18.09, and the next major release for Edge for Private Cloud will be 19.01, targeted for January 2019.

Apigee Edge for Private Cloud’s support terms and conditions will also change based on customer feedback and to align with the new release process. The new terms for supporting Edge for Private Cloud will be N-2 versions (where N is a major release). Previously, support was for the previous 12 months.

When Edge for Private Cloud 19.01 is released, you must be on 18.01 or 18.05 to continue to receive support. Apigee will continue to release minor (or, "dot") releases and patches for supported versions as needed.

Getting release notifications

You can sign up to receive release notifications by going to this page and clicking the Subcribe to Updates button.

About release numbering

Release numbers represent approximate release dates. For example:

  • Public Cloud release 17.10.09 roughly corresponds to October 9, 2017.
  • Private Cloud release 4.17.09 roughly corresponds to September 2017.

Private Cloud releases contain Public Cloud releases. You can guesstimate whether a Public Cloud release is included in a Private Cloud release by comparing version numbers. In the examples above, you could guess that Public Cloud release 17.10.09 is not in Private Cloud release 4.17.09, since October 9, 2017 is after September 2017. For an official view of which Public Cloud releases are in a Private Cloud release, see the Private Cloud release notes for a major revision (Feature Release).

Apigee Edge Public Cloud

  • Release windows are every Monday through Thursday.
  • During the release window, you will see information about a release in progress when you go to https://status.apigee.com.
  • Upon completion of the release, you can find release notes at http://apigee.com/docs/release-notes/content/apigee-edge-release-notes.
  • All releases are expected to be free of interruption to Apigee Edge, unless it is a planned downtime, which will be done with minimum of 5 business days notification.
  • Our Global Services Center (GSC) will be available 24x7 as usual and during the release windows if you need to raise a support ticket.
  • Hot fixes or emergency patches, due to their time-critical nature, are excluded from this process and will be released with urgency and as soon as possible without prior notification.
  • Releases use the following numbering scheme: YY.MM.DD.

Apigee Edge for Private Cloud (on-premises)

  • Types of releases include:
    • 2 major releases per year (called "Feature Releases"): on the last Tuesday of January and June

      All Feature Releases are maintained for 1 year, with defects resolved through service packs (4.15.07 and earlier) or updates (4.16.01 and later)

    • Updates for Feature Releases as needed
    • Unplanned hot fix for any particular release as needed
  • Feature Releases
    • Contain:
      • New features and enhancements
      • Cumulative bug fixes
      • Infrastructure/architecture changes
      • Database schema changes
      • Security vulnerability mitigation
      • Configuration changes
      • Installer changes
      • Documentation changes
    • Are based on Public Cloud release that occurred 6-8 weeks prior to the scheduled Private Cloud release
  • Updates
    • Contain:
      • Cumulative bug fixes
      • Security vulnerability mitigation
      • Configuration changes
      • Installer changes
      • Documentation changes
      • May include, at Apigee's sole discretion, minor enhancements
    • Are delivered at Apigee's sole discretion, typically within 3-6 weeks of identification of root cause of defect
    • Are applicable to a specific Feature Release
    • Are maintained under the process for Feature Release
  • Hot Fixes
    • Include:
      • Targeted critical bug fixes
      • Targeted security vulnerability mitigation
    • Are delivered at Apigee's sole discretion, typically within 5-7 days of identification of root cause of defect
    • Are applicable to a specific Feature Release
  • Support timelines: Updates and hot fixes will be provided for any Feature Release for the following 1 year. After that time period, Apigee requires customers to upgrade to a current Feature Release. No support tickets will be accepted for any releases that are outside the support window.
  • For more information, see Apigee Edge release notes.
  • Releases use the following numbering scheme: 4.YY.MM.##, where ## is the update number. Feature Releases are 4.YY.MM.