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-requ...@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
signature.asc
Description: OpenPGP digital signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
