From 4f0412444f2f41b8cb12f5911cea37052dc0c62c Mon Sep 17 00:00:00 2001 From: XiaojueGuan Date: Tue, 12 Jun 2018 16:43:59 +0800 Subject: [PATCH] Update links in README Change the outdated links to the latest links in README Change-Id: I866068aabce6a5be2e6fee4d9f286b776cf008c7 --- doc/source/contributor/rolling-upgrades.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/contributor/rolling-upgrades.rst b/doc/source/contributor/rolling-upgrades.rst index cc5d531219..2c0895a01a 100644 --- a/doc/source/contributor/rolling-upgrades.rst +++ b/doc/source/contributor/rolling-upgrades.rst @@ -22,7 +22,7 @@ We refer to a ``named release`` of ironic as the release associated with a development cycle like Pike. In addition, ironic follows the `standard deprecation policy -`_, +`_, which says that the deprecation period must be at least three months and a cycle boundary. This means that there will never be anything that is both deprecated *and* removed between two named releases. @@ -98,7 +98,7 @@ The policy for changes to the DB model is as follows: * The dropping of columns or tables and corresponding objects' fields is subject to ironic's `deprecation policy - `_. + `_. But its alembic script has to wait one more deprecation period, otherwise an ``unknown column`` exception will be thrown when ``FromVer`` services access the DB. This is because :command:`ironic-dbsync upgrade` upgrades the