From 6fb097dcb754849cb33a365dfae05c92aea78944 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ivar=20Conradi=20=C3=98sthus?= Date: Fri, 17 Nov 2017 13:04:20 +0100 Subject: [PATCH] Update migration-guide.md Add details on how to upgrade unleash to version 3. closes #276 --- docs/migration-guide.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/migration-guide.md b/docs/migration-guide.md index c89761cf5c..63c0870389 100644 --- a/docs/migration-guide.md +++ b/docs/migration-guide.md @@ -1,6 +1,14 @@ # Migrations guide +Generally the intention is that `unleash-server` should always provide support for clients one lower major version. This should make it easier to upgrade `unleash` gradually. -## Upgrading from v1.0 to 2.0 + +## Upgrading from v2.x to v3.x +Upgrade `unleash-server` to v3, which still supports v2 clients. Then upgrade all your clients to v3. When you have upgraded all your clients you should consider to turn off legacy routes, used by v2 clients. Read more about this option in in the [gettings started guide](https://github.com/Unleash/unleash/blob/master/docs/getting-started.md#2-or-programmatically) + + + + +## Upgrading from v1.0 to v2.0 ### Caveat 1: Not used db-migrate to migrate the unleash database? In FINN we used, for internal reasons, liquebase to migrate our database.