Sounds good to me yeah, it's easier to track down the updates to do I think Le 11 juin 2013 à 21:51, Lorin Hochstein <lorin at nimbisservices.com> a écrit : > Tom's DocImpact automation proposal <https://review.openstack.org/25887> got me thinking more generally about DocImpact and new features. > > I would like to propose to the opentack-dev mailing list that for commits that require doc changes ("DocImpact"), there must be sufficient information in the commit message for a member of the doc team to use this info to update the docs (i.e., we shouldn't need to go splunking through the code diff). > > If there isn't enough info in the commit log, then it should be socially acceptable to vote "-1" on the proposed code change. > > Does that sound reasonable? > > Lorin > > -- > Lorin Hochstein > Lead Architect - Cloud Services > Nimbis Services, Inc. > www.nimbisservices.com > _______________________________________________ > Openstack-docs mailing list > Openstack-docs at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20130611/67a10957/attachment.html>