Add support_status doc for properties

Bug #1376868 reported by Gauvain Pocentek
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Low
Steven Hardy

Bug Description

support_status information should be provided in the HOT reference. See https://review.openstack.org/#/c/116443/ for reference.

Revision history for this message
Gauvain Pocentek (gpocentek) wrote :

support_status for properties...

Changed in heat:
assignee: nobody → Gauvain Pocentek (gpocentek)
Angus Salkeld (asalkeld)
Changed in heat:
status: New → Triaged
importance: Undecided → Low
milestone: none → next
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to heat (master)

Fix proposed to branch: master
Review: https://review.openstack.org/147434

Changed in heat:
assignee: Gauvain Pocentek (gpocentek) → Steven Hardy (shardy)
status: Triaged → In Progress
Steven Hardy (shardy)
Changed in heat:
milestone: next → kilo-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to heat (master)

Reviewed: https://review.openstack.org/147434
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=144f5e49b96ad8bc6bab6e35e44e72af5c31475e
Submitter: Jenkins
Branch: master

commit 144f5e49b96ad8bc6bab6e35e44e72af5c31475e
Author: Steven Hardy <email address hidden>
Date: Thu Jan 15 09:41:57 2015 +0000

    Add support status to docs for properties

    I thought we already had this, but inspection of the generated docs
    reveals that we only do class-level docs for the support status,
    not exposing those defined in the schema.

    Adding the properties support status should help reduce user confusion
    when new properties are added between releases.

    Change-Id: I5f3228161e57daad73cbafc124c4fad05c68d3d6
    Closes-Bug: 1376868

Changed in heat:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in heat:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in heat:
milestone: kilo-2 → 2015.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.