Apigee release process

This topic describes the release process for Apigee products.

Introduction

Apigee Edge follows a continuous release model for the Public Cloud, Private Cloud, Apigee hybrid, and Edge Microgateway products 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 the products, unless it is a planned downtime which will be done with minimum of five business days notification. As Apigee products provide a mission-critical infrastructure that enables access to enterprise services by developers, customers, employees and partners, new 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

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 for Public and Private Cloud represent approximate release dates. For example:

  • Public Cloud release 19.03.01 roughly corresponds to March 1, 2019.
  • Private Cloud release 4.19.01 roughly corresponds to January 2019.

Private Cloud releases contain Public Cloud releases. You can tell whether a Public Cloud release is included in a Private Cloud release by comparing version numbers. In the examples above, you could see that Public Cloud release 19.03.01 is probably not in Private Cloud release 4.19.01, since March 1, 2019 is after January 2019. 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 process

  • 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 release process

This section describes the release process for Apigee Edge for Private Cloud.

Release cadence

There will be two Apigee Edge for Private Cloud releases per year. Support terms and conditions have changed to align with the new release process. The terms for supporting Edge for Private Cloud are N-2 versions (where N is a major release). Previously, support was for the previous 12 months.

For example, when Edge for Private Cloud 4.20.03 is released, you must be on 4.19.06 or 4.19.01 to continue to receive support. Apigee will continue to release minor (or, "dot") releases and patches for supported versions as needed.

Installer downloads

Edge for Private Cloud version 4.16.01 and later, use the credentials you received from Apigee to:

Types of releases

  • 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

Feature releases contain the following:

  • New features and enhancements
  • Cumulative bug fixes
  • Infrastructure/architecture changes
  • Database schema changes
  • Security vulnerability mitigation
  • Configuration changes
  • Installer changes
  • Documentation changes

Feature releases are based on Public Cloud release that occurred 6-8 weeks prior to the scheduled Private Cloud release

Updates

Updates contain the following:

  • Cumulative bug fixes
  • Security vulnerability mitigation
  • Configuration changes
  • Installer changes
  • Documentation changes
  • May include, at Apigee's sole discretion, minor enhancements

Updates are:

  • Delivered at Apigee's sole discretion, typically within 3-6 weeks of identification of root cause of defect
  • Applicable to a specific Feature Release
  • Maintained under the process for Feature Release

Hot fixes

Hot fixes include:

  • Targeted critical bug fixes
  • Targeted security vulnerability mitigation

Hot fixes are:

  • Delivered at Apigee's sole discretion, typically within 5-7 days of identification of root cause of defect
  • Applicable to a specific Feature Release

Support timelines

Support timelines: Updates and hot fixes will be provided for any of the previous N-2 versions, where N is a major release. After that support window expires, 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.

Apigee hybrid release process

This section describes the versioning scheme, release cadence, and support timelines for Apigee hybrid. For more information, see the Release notes.

Release versioning and cadence

Releases for Apigee hybrid use the following numbering scheme: Major.Minor.Patch. For example, 3.2.1, where the major number is 3, the minor number is 2, and the patch number is 1.

Release degree Release cadence Description
Major As needed Major releases may contain new features and enhancements, cumulative bug fixes, security vulnerability mitigation, configuration changes, and infrastructure/architecture changes.
Minor Quarterly Minor releases may contain existing feature enhancements, cumulative bug fixes, and security vulnerability mitigation.
Patch Monthly Patch releases may contain bug fixes and targeted security vulnerability mitigation.

Management plane compatibility and support timelines

Apigee hybrid management plane will remain compatible with and be supported to work with a new hybrid runtime release for 12 months after the runtime version is published (or the greater of the last 4 runtime releases and 12 months).

A management plane upgrade may break a runtime version that was published 12 months or longer.

After the support window expires, Apigee requires customers to upgrade to a current release. No support tickets will be accepted for any releases that are outside the support window.

Notification

Apigee will collect and store hybrid runtime versions in the management plane. This information will be used to notify customers who are at risk of operating hybrid runtime on a version that will no longer be supported by Apigee.

Edge Microgateway release process

This section describes the versioning scheme, release cadence, and support timelines for Edge Microgateway. For more information, see the Release notes.

Release versioning scheme

Releases for Edge Microgateway use the following numbering scheme: Major.Minor.Patch. For example, 3.2.1, where the major number is 3, the minor number is 2, and the patch number is 1.

Release degree Description
Minor Major releases may contain new features and enhancements, cumulative bug fixes, security vulnerability mitigation, configuration changes, and infrastructure/architecture changes.
Minor Minor releases may contain existing feature enhancements, cumulative bug fixes, and security vulnerability mitigation.
Patch Patch releases may contain bug fixes and targeted security vulnerability mitigation.

Release cadence

Apigee will release a new version of Edge Microgateway approximately once a month; however, this monthly release cadence is subject to change and may be longer or shorter as circumstances require. A release may be a Major, Minor, or Patch version.

Support timelines

The current version of Edge Microgateway will continue to be supported for one year after the next version becomes available.

For example, if version 3.1.0 is released on January 17, 2020 and version 3.1.1 is released on February 17, 2020, version 3.1.0 will be supported until February 17, 2021.

After the support window expires, Apigee requires customers to upgrade to a current release. No support tickets will be accepted for any releases that are outside the support window.