Release Timelines
Major Releases
Major releases let us roll out new features and functionality in a controlled manner. To help you plan for each major release, we want to provide visibility and predictability with our release schedule. This way you have ample time to plan your upgrade activities and test the release before it goes to production on your specified release date.
We roll out major releases three times per year, in January, May, and September. See Upcoming Coupa Release Schedule for the dates of upcoming releases.
| Step | Lead Time | Description |
|---|---|---|
|
Sandbox update notification |
6 weeks |
We notify you of the new release and when we’ll upgrade your sandbox and production instances. With our fixed release schedule you can start planning for these dates months in advance. You will be provided a choice of three dates for your production update. |
| Release notes availability | 4 weeks | We update success.coupa.com with the latest release notes. |
|
Sandbox update |
1 to 4 weeks |
We upgrade the new release to your sandbox instance based on your assigned schedule. Talk to your Customer Value Manager if you have specific needs. |
|
Production update notification |
2 weeks |
We remind you that we’ll be upgrading your production instance to the new release. |
|
Production update |
0 weeks |
We update your production instance to the new release. |
Maintenance Updates
Maintenance updates allow us to address issues that affect customers in a scheduled manner. Code changes are signed off and pass our internal quality certification every other Friday. That same Friday, we deploy the maintenance update to our own internal production environment here at Coupa. Our release communications include release notes, explaining the changes in the maintenance update.
| Step | Step Day | Description |
|---|---|---|
|
Update notification |
Wednesday |
We notify you of the pending maintenance update and provide release notes describing the issues we resolved. |
|
Sandbox update |
We update your sandbox instance with the new maintenance update. |
|
|
Production update notification |
Wednesday |
We remind you that we'll be updating your production instance to the new maintenance update release. |
|
Production update |
Friday |
We update your production instance to the new maintenance update. |
Daily Updates
Daily updates address critical issues that impact a majority of our customers. Even though they're rare, it's in your best interest to get these updates as soon as they're ready. Since a daily update is much smaller than a maintenance update, there's no risk to your production instance. We'll update both your sandbox and production instances at the same time.
| Step | Step Day | Description |
|---|---|---|
|
Daily Update Notification |
ASAP |
We notify you that we need to update your instance as soon as we know when we'll be deploying the daily update. This is usually the day before or the day of the update, with a few hours notice. |
|
Sandbox update |
Date provided in the notification |
We update your sandbox instance to the daily update. |
| Production update |
Date provided in the notification |
We update your sandbox instance to the daily update. |
The Major Releases, Maintenance Updates, and Daily Updates will automatically be deployed to your sandbox and production environments. We sometimes refer to this mechanism as the auto-update train.