From 46ba2f8366a42d5dc549f23e7c36534bd840785f Mon Sep 17 00:00:00 2001 From: Thomas Gelf Date: Fri, 10 Aug 2018 14:00:03 +0200 Subject: [PATCH] doc/upgrading: new section for v1.5.x --- doc/05-Upgrading.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/doc/05-Upgrading.md b/doc/05-Upgrading.md index 30b9c536..27fb335e 100644 --- a/doc/05-Upgrading.md +++ b/doc/05-Upgrading.md @@ -16,6 +16,7 @@ you will be told so in your frontend. Please read more about: * [Database Backup](#backup-first) +* [Upgrading to 1.5.x](#upgrade-to-1.5.x) * [Upgrading to 1.4.x](#upgrade-to-1.4.x) * [Upgrading to 1.3.0](#upgrade-to-1.3.0) * [Upgrading to 1.2.0](#upgrade-to-1.2.0) @@ -36,6 +37,16 @@ use the tools provided by your database backend, like `mysqldump` or `pg_dump`. Restoring from a backup is trivial, and Director will always be able to apply pending database migrations to an imported old database snapshot. +Upgrading to 1.5.x +------------------------------------------------- + +There is nothing special to take care of. In case you are running 1.4.x or any +GIT master since then, all you need is to replace the Director module folder +with the new one. Or to run git checkout v1.5.0 in case you installed Director +from GIT. + +As always, you'll then be prompted to apply pending Database Migrations. + Upgrading to 1.4.x -------------------------------------------------