Google is committed to advancing racial equity for Black communities. See how.

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.

Apigee Edge Public Cloud release process

About release numbering

Releases use the following numbering scheme: YY.MM.DD, where:

  • YY is the two-digit year in which the release occurred.
  • MM is the two-digit month in which the release occurred.
  • DD is the day of the month on which the release occurred.

Release numbers for Public Cloud represent approximate release dates. For example, Public Cloud release 19.03.01 roughly corresponds to March 1, 2019.

Release windows

  • 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://docs.apigee.com/release/notes/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.

Apigee Edge for Private Cloud release process

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

Versioning numbering scheme

Starting with 4.50.00, Apigee Edge for Private Cloud releases will use the following version numbering scheme: 4.5N.XX-YY.ZZ.BBBB, where:

Number part Description
5N Starting with 50, this number will increment by 1 for each major release.
XX Starting with 00, this number will increment by 1 for each minor release.
YY Starting with 00, this number will increment by 1 for each patch release.
ZZ Starting with 00, this number is reserved hotfixes only.
BBBB The internal build number of the release.

For example, after release (4.50.00), the next minor release would be 4.50.01.YY.ZZ.BBBB. A patch release after that would be 4.50.01-01.ZZ.BBBB.

Types of releases and their cadences

With the release of Apigee Edge for Private Cloud version 4.50.00, Apigee will move away from the twice-yearly release versions and instead do releases as frequently as once a month and hot fixes as soon as possible when needed.

Release type Cadence
Major and minor versions As needed, up to twice per year.
Patches Once per month, if there are priority issues to be resolved for customers.
Hot fixes As soon as possible, if needed.

Release type descriptions

Apigee Edge for Private Cloud has the following types of releases:

Release type Description
Major or minor May include cumulative bug fixes, configuration changes, installer changes, documentation changes, enhancements, features, and security vulnerability mitigation.
Patch Priority issues that are resolved for customers.
Hot fix Targeted critical bug fixes and security vulnerability mitigation.

Support timelines

With the release of Apigee Edge for Private Cloud version 4.50.00, support will no longer be provided for version 18.05 and prior versions. Once the support window has expired, support cases submitted will not be addressed until after the customer has upgraded to a supported version of the product. If you are running unsupported versions, you will be required to upgrade to a supported version of the product.

  • Apigee Edge for Private Cloud version 19.01 will be supported until December 31, 2020.
  • Apigee Edge for Private Cloud version 19.06 will be supported until May 31, 2021.

After June 01, 2021, you are recommended to be on Apigee Edge for Private Cloud version 4.5N.XX. From that point, support will only be provided for the latest version and any version releases or patches in the prior 18 months. Applying bug fixes will require moving to the latest patch on the major/minor version you are on.

Installer downloads

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

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