On 24 November 2015 at 13:11, Lana Brindley
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi Akihiro,
>
> Judging by most of the bugs we see in the openstack-manuals queue, the
> bugs that will be raised in projects' own queues will usually be against
> their own developer docume
These changes have merged now,
Andreas
On 2015-11-23 23:33, Lana Brindley wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi everyone,
The DocImpact flag was implemented back in Havana to make it easier for
developers to notify the documentation team when a patch might cause a change
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Akihiro,
Judging by most of the bugs we see in the openstack-manuals queue, the bugs
that will be raised in projects' own queues will usually be against their own
developer documentation. In the rare instance that that isn't the case, and it
n
it sounds a good idea in general.
One question is how each project team should handle DocImpact bugs
filed in their own project.
It will be a part of "Plan and implement an education campaign"
mentioned in the docs spec.
I think some guidance will be needed. One usual question will be which
guide(
