Send Docs Feedback

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 5 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.

Getting release notifications

See Get release notifications.

About release numbering

Release numbers represent approximate release dates. For example:

  • Public Cloud release 16.03.02 roughly corresponds to March 2, 2016.
  • Private Cloud release 4.15.07.xx roughly corresponds to July 2015.

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 16.03.02 is not in Private Cloud release 4.15.07, since March 2, 2016 is after July 2015. 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 Window Change for Holiday Season

In order to complete all scheduled changes prior to the start of our holiday season moratorium, we will be following an extended release window schedule until Nov 1, 2016. Instead of our standard Tuesday through Thursday release window, releases will now happen every day of the week during the following hours:

Time zone Countries
Australia & Asia Pacific
(UTC+8): 12am-4am
Countries
Europe 
(UTC+2): 12am-4am
Countries
Americas
(UTC-4): 12am-4am
(UTC-7): 12am-4am

Countries (U.S. Eastern)
(U.S. Pacific)
  • During the release window, you will see a notification of release in progress when you log in at https://edge.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)

Installer downloads - Edge for Private Cloud version 4.16.01 and later: Use the credentials you received from Apigee to:

  • Types of releases include:
    • 3 major releases per year (called "Feature Releases"): on the last Tuesday of January, May, and September.
      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 those time periods, Apigee will either provide a workaround for issues or, if no workaround exists, have customers upgrade to the current Feature Release.
  • For release notes, see http://apigee.com/docs/release-notes/content/apigee-edge-release-notes.
  • Releases use the following numbering scheme: 4.YY.MM.##, where ## is the update number. Feature Releases are 4.YY.MM.

Help or comments?