From 2125afb2f5e492b749098c718a602a8e8083fefb Mon Sep 17 00:00:00 2001 From: David Alexander Date: Tue, 23 Jun 2015 11:57:54 +1200 Subject: [PATCH] DOCS: fixed broken link --- docs/en/03_Upgrading/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/03_Upgrading/index.md b/docs/en/03_Upgrading/index.md index e051ff8ae..825876142 100644 --- a/docs/en/03_Upgrading/index.md +++ b/docs/en/03_Upgrading/index.md @@ -40,7 +40,7 @@ Never update a website on the live server without trying it on a development cop How easy will it be to update my project? It's a fair question, and sometimes a difficult one to answer. -* "Micro" releases (x.y.z) are explicitly backwards compatible, "minor" and "major" releases can deprecate features and change APIs (see our [/misc/release-process](release process) for details) +* "Micro" releases (x.y.z) are explicitly backwards compatible, "minor" and "major" releases can deprecate features and change APIs (see our [/misc/release-process](../contributing/release_process) for details) * If you've made custom branches of SilverStripe core, or any thirdparty module, it's going to be harder to upgrade. * The more custom features you have, the harder it will be to upgrade. You will have to re-test all of those features, and adapt to API changes in core. * Customizations of a well defined type - such as custom page types or custom blog widgets - are going to be easier to upgrade than customisations that modify deep system internals like rewriting SQL queries.