I agree with Matt here, let's just close this bug report and use the
blueprint "api-ref-in-rst" to drive this. The effort is described on the
ML [1] and the wiki [2]. The file the bug reporter is referencing to
has a comment at the top which describes the needed cleanup tasks [3].
Long story short, push the patch you planned to do but reference the bp instead of the bug.
I agree with Matt here, let's just close this bug report and use the
blueprint "api-ref-in-rst" to drive this. The effort is described on the
ML [1] and the wiki [2]. The file the bug reporter is referencing to
has a comment at the top which describes the needed cleanup tasks [3].
Long story short, push the patch you planned to do but reference the bp instead of the bug.
References: lists.openstack .org/pipermail/ openstack- dev/2016- April/092936. html /wiki.openstack .org/wiki/ NovaAPIRef# Parameter_ Verification /github. com/openstack/ nova/blob/ master/ api-ref/ source/ servers. inc#L3
[1] [openstack-dev] [nova] api-ref content verification phase doc push
http://
[2] https:/
[3] https:/