VIP Go platform specific
This document is for sites running on VIP Go.
The VIP team manages the process of upgrading WordPress to a major new version when it is released. For non-security releases, we are happy to upgrade a non-production environment to the new release so you can validate your applications before we upgrade you. For security releases, we will update all applications as soon as possible.
We want you to be able to use the latest and greatest version of WordPress on the planet! Please make sure you develop and test against the latest version of WordPress available in trunk.
Major Versions, e.g. 1.1 #
We consider a major new version of WordPress to be X.X, e.g. 5.1, 5.2, etc.
We expect development teams to be testing WordPress releases through the beta and release candidate periods, including switching over your local environment to use the beta tester plugin or a SVN checkout of trunk. If you would like to test your application on the new version of WordPress on a non-production environment before upgrading, please contact us.
Details of major updates are posted in the VIP Lobby, including details of recommended testing. This upgrade post will include a date when we expect to upgrade all applications to the new version, if you have any issues with the timeline please contact us to discuss and we will do our best to accommodate issues of importance to your organisation.
Minor Versions, e.g. 1.1.1 #
WordPress minor releases are designed to change the most minimal set of code to fix a given group of bugs. Accordingly they are considered low risk upgrades.
Upgrades to minor releases are run in a similar fashion to major version releases: we will make the upgrade as soon as possible after the release occurs.
Security Releases #
When a security release comes out, we will deploy it to all VIP Go applications as soon as possible.
Where possible, we will deploy patches and other protections to mitigate undisclosed security issues that we are aware of.