Open Stack

No trouble. Yes, the config changes should be picked up automatically. You can't edit those files in the book directly, as a script writes them. That's why your change would have been declined.

Thanks for asking the question, though :)

L

On 24/04/16 11:12, ZhiQiang Fan wrote:
> Hi Lana,
> 
> Thank you for explaining it! 
> 
> Yes, I noticed that the DocImpact bug track now has shifted to project its own, that why I submit a change by using the tool in openstack-doc-tools, but that change is disagreed by a doc core. Meanwhile I also find that there is rarely change merged for config reference update.
> 
> So I want to know is the config reference automatically updated so no more individual commit is required?
> 
> Best Regards,
> 
> On Sun, Apr 24, 2016 at 11:28 PM, Lana Brindley <openstack at lanabrindley.com <mailto:openstack at lanabrindley.com>> wrote:
> 
>     Hi ZhiQiang,
> 
>     I am not sure I understand your question. The only change to DocImpact is that now the bug is created in the project's bug queue, not OpenStack manuals. There is no other automation for DocImpact.
> 
>     For the config ref, there is a script that we run to get any new changes. That will happen whether or not there is a DocImpact bug.
> 
>     Does that answer your question?
> 
>     Thanks,
>     Lana
> 
>     On 23/04/16 19:00, ZhiQiang Fan wrote:
>     > Hi Doc Team,
>     >
>     > I want to know the recent status of DocImpact tag, is it deprecated for config option changes now? If it's true, then what the workflow for config reference now, any hint or link?
>     >
>     > Previously, when a patch has impact to document, including config option changes, I usually ask contributors to add a DocImpact, hence there will be a bug track the document issue.
>     >
>     > Recently, a patch lands in Ceilometer which adds two new options, and Ceilometer receives the auto created document bug. However, when I submit a patch to openstack-manuals to fix it, I was told by a core that such change is not needed any more, I searched latest merged patch in openstack-manuals and found what he said is true, but still don't know why and what action I should follow in Ceilometer/Aodh projects
>     >
>     > Thank you very much!
>     >
>     > ZhiQiang Fan
>     >
>     >
>     > __________________________________________________________________________
>     > OpenStack Development Mailing List (not for usage questions)
>     > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>     > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>     >
> 
>     --
>     Lana Brindley
>     Technical Writer
>     Rackspace Cloud Builders Australia
>     http://lanabrindley.com
> 
> 
>     __________________________________________________________________________
>     OpenStack Development Mailing List (not for usage questions)
>     Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 

-- 
Lana Brindley
Technical Writer
Rackspace Cloud Builders Australia
http://lanabrindley.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 538 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160426/743311a8/attachment.pgp>