EPS Rapid Versioning Schedule

EPS Rapid Versioning

EPS releases a new version of EPS Rapid twice a year (one every 6 months).

We maintain 3 production versions (i.e. version 2.2, 2.3, and 2.4) with one always in development (i.e. the currently unreleased 2.5).

This provides you, our partner, with a certain amount of flexibility to choose your update schedule when new versions are released.  

Please note that we have delayed sunset of older versions of EPS Rapid until 2020. This means that EPS Rapid 2.0 and 2.1 will be deprecated at the same time in order to maintain our versioning schedule. The normal life cycle of our API revisions is outlined below.

API Platform Versioning

Overview

Currently, the EPS Technology teams maintain two stable versions of the API, one version that is in a Deprecated status and one scheduled for end of life (Sunset).

Change is inevitable and growth is a good thing.  

A few definitions of some of the concepts that we talk about:

Development: Development phase of the upcoming version. It is recommended that developers begin preparing for the upcoming changes.

Active: The current, active version available. There will be no schema changes on the available endpoints.

Deprecation: When a version is marked for deprecation, it is an indication that the version will no longer be available in 6 months. This is a good time to start updating to an active version.

*The only changes that should be made to a deprecated version would be for security issues or bugs.

Sunset: Once a version is sunset, that version will no longer be accessible via the API.

Strategy

Moving forward, our API will be updated every 6 months with new features and improvements. These changes also allow us to add robustness and reliability.

Example timeline:

Month 1

• Version A becomes Active (Development)
• Notify Partners of new API (Product, Partner Connect)
• Start reviewing schema changes for upcoming Version B (Development)

Month 2

• Review schema changes in development for Version B (Development)
• Publish new Version B features to Partners (Product)
• Final list of API changes for Version B defined (Product and Development)

Month 3

• Review with Development scheduled for Version B changes (Architecture)
• Complete review of Version B API changes, provide feedback to Architecture and Development (Partner Connect)
• Final review meeting for API changes in Version B with Development (Architecture)

Month 4

• Start of month, publish schema for Version B (Development)
• Provide schema to product for external publication (Architecture)
• Publish stubs and new schema to test endpoint (Development)

Month 5

• Development continues on Version B (Development)
• Research features for Version C (Product, Partner Connect)
• Development continues to push new features to test endpoint for Version B (Development) 

Month 6

• Development continues on Version B (Development)
• Research features for Version C (Product, Partner Connect)
• Provides Version C features for upcoming quarterly planning (Product)

• Two weeks prior to end of quarter, all new Version B features available on test endpoint (Development)

Month 12

• Version A goes into Deprecated status (Development) 
• Version C goes into Production (Development)

Month 18

• Version A goes into Sunset status (Development)
• Version B goes into Deprecated status (Development)

Deprecation Schedule

Below is the version that will be deprecated and scheduled to be sunset: