[openstack-dev] [Neutron] DocImpact flag: a kind reminder

Hirofumi Ichihara ichihara.hirofumi at lab.ntt.co.jp
Mon Feb 29 23:34:55 UTC 2016

Hi Armando,

I didn't know and I have such patch now.
Thank you for your message.

I have seen that neutron spec has the flag in the Commit Message.
In such case, we don't need to add the flag into the implementation 
patch, do we?


On 2016/03/01 7:18, Armando M. wrote:
> Hi Neutrinos,
> Please remember that what you decorate a commit message with 
> DocImpact, this must be followed by a brief description of the 
> documentation impact [1]. Also, please be aware that currently, as 
> soon as the patch merges, a bug report is filed against the Launchpad 
> project of the targeted repo. This is tagged with 'doc' and 
> '<repo-name>' [2].
> So, if you have a train of patches affecting the same feature (client 
> side, server side, *-aas projects etc), be mindful to where you put 
> the tag and avoid adding DocImpact to more than one commit message, 
> unless the documentation target is indeed meant to be separate.
> Cheers,
> Armando
> [1] 
> http://lists.openstack.org/pipermail/openstack-dev/2015-November/080294.html
> [2] https://bugs.launchpad.net/neutron/+bugs?field.tag=doc
> __________________________________________________________________________
> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160301/f4c472f8/attachment.html>

More information about the OpenStack-dev mailing list