From b3843ee352bfc4f13bdfe2ccce646234bf578128 Mon Sep 17 00:00:00 2001 From: Matt Riedemann Date: Mon, 8 Jan 2018 21:13:08 -0500 Subject: [PATCH] Qualify the Placement 1.15 release note When reading the nova release notes together, it might be easy for someone to not realize this release note is talking about the Placement API, so this change adds that qualifier to the note. Change-Id: Iaa845c246329626b52c1a822e0c8b214b2af04c2 --- .../placement-last-modified-cf43aece4c54fc97.yaml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/releasenotes/notes/placement-last-modified-cf43aece4c54fc97.yaml b/releasenotes/notes/placement-last-modified-cf43aece4c54fc97.yaml index f97780a56498..284c9ee55c6a 100644 --- a/releasenotes/notes/placement-last-modified-cf43aece4c54fc97.yaml +++ b/releasenotes/notes/placement-last-modified-cf43aece4c54fc97.yaml @@ -1,10 +1,10 @@ --- features: - | - Throughout the API, in microversion 1.15, 'last-modified' headers have been - added to GET responses and those PUT and POST responses that have bodies. - The value is either the actual last modified time of the most recently - modified associated database entity or the current time if there is no - direct mapping to the database. In addition, 'cache-control: no-cache' - headers are added where the 'last-modified' header has been added to - prevent inadvertent caching of resources. + Throughout the Placement API, in microversion 1.15, 'last-modified' headers + have been added to GET responses and those PUT and POST responses that have + bodies. The value is either the actual last modified time of the most + recently modified associated database entity or the current time if there + is no direct mapping to the database. In addition, + 'cache-control: no-cache' headers are added where the 'last-modified' + header has been added to prevent inadvertent caching of resources.