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 will work with you to provide a test environment so you can validate your applications before we upgrade you. For security releases, we will update all sites 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. 4.3, 4.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. You will also need contact us to request for your development environment to be updated to trunk. This is to make sure you’re running the latest version and can test for any issues before they are rolled out.
Details of major update content is posted in the VIP Lobby, including details of recommended testing.
Once the release occurs, we will update all VIP Go sites to the new version as soon as possible.
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 sites as soon as possible.
Where possible, we will deploy patches and other protections to mitigate undisclosed security issues that we are aware of.