Re: [openstack-dev] [openstack-manuals] What the status of DocImpact

Thanks, @Matt and @Doug, I agree that it's time to consider project holds its document in its own repository. There is a gap between document team and our projects source code, even though they are excellent and working hard, but our source code is growing fast in the same time, this problem is

Re: [openstack-dev] [openstack-manuals] What the status of DocImpact

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, > >

Re: [openstack-dev] [openstack-manuals] What the status of DocImpact

Excerpts from Matt Riedemann's message of 2016-04-24 15:54:03 -0500: > On 4/24/2016 8:03 AM, ZhiQiang Fan wrote: > > but Document Team has so beautiful tables, and so convenient tools > > , it is a huge waste of resource if we manually > > write it to release note in each project. > > > > So I

Re: [openstack-dev] [openstack-manuals] What the status of DocImpact

On 4/24/2016 8:03 AM, ZhiQiang Fan wrote: but Document Team has so beautiful tables, and so convenient tools , it is a huge waste of resource if we manually write it to release note in each project. So I want to figure out what have happened to prevent Document Team continuing previous

Re: [openstack-dev] [openstack-manuals] What the status of DocImpact

Thank you, Sir! On Mon, Apr 25, 2016 at 2:25 AM, Andreas Jaeger wrote: > On 04/24/2016 11:12 AM, 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

Re: [openstack-dev] [openstack-manuals] What the status of DocImpact

On 04/24/2016 11:12 AM, 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

Re: [openstack-dev] [openstack-manuals] What the status of DocImpact

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

Re: [openstack-dev] [openstack-manuals] What the status of DocImpact

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

Re: [openstack-dev] [openstack-manuals] What the status of DocImpact

but Document Team has so beautiful tables, and so convenient tools , it is a huge waste of resource if we manually write it to release note in each project. So I want to figure out what have happened to prevent Document Team continuing previous workflow. Thanks On Sun, Apr 24, 2016 at 8:54 PM,

Re: [openstack-dev] [openstack-manuals] What the status of DocImpact

Excerpts from ZhiQiang Fan's message of 2016-04-24 08:00:10 +0800: > 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