[Openstack-docs] How to deal with DocImpact patches

Summer Long slong at redhat.com
Mon Mar 31 23:56:52 UTC 2014


Hi again,
Was hoping someone would chime in with the further problem of not noting doc bugs or review for docs in the dev space.
*  Could the automatic process for a DocImpact dev bug note somewhere that the doc bug has been created?
*  For patches without 'DocImpact', could we note somewhere that the dev bug has been reviewed for doc impact?

Thanks, Summer

-- 
Summer Long 
OpenStack Documentation Lead 
Engineering Content Services 

Red Hat Asia Pacific 
Brisbane, Australia 
slong at redhat.com | irc: slong 

----- Original Message -----
> From: "Tom Fifield" <tom at openstack.org>
> To: openstack-docs at lists.openstack.org
> Sent: Monday, March 31, 2014 4:37:11 PM
> Subject: Re: [Openstack-docs] How to deal with DocImpact patches
> 
> On 31/03/14 13:51, Summer Long wrote:
> > Hello all,
> > Here's something I've hit more than once.
> > I'm seeing a blueprint with a change that says 'DocImpact'. But I cannot
> > find the related docs bug, although this should have been created
> > automatically, right?
> >
> > We had a chat about this at the last design conference. There's no way to
> > easily see or find the attached docs bug. And if there isn't a bug,
> > there's no way to see 'yes, someone has looked at this. No, there's no
> > impact'. Which in this case, there's not (it's a small change, and it will
> > be automatically included in the Config Ref).
> >
> > Should we say that a comment should be placed on the attached Blueprint's
> > whiteboard? But what about patches without whiteboards?
> >
> > Am I just being blind (granted, am tired today)?
> >
> > thanks, Summer
> 
> Best way I've found is to use the change ID, eg
> 2cbea242092dabf4c54544d5c8c32ba4b5fb8a1f
> 
> Put that in google and you get the review and the bug.
> 
> 
> Having said that, I have a theory as to why some are not being created -
> false positive matches from the anti-duplicate code that we no longer
> need. Hope that this patch will fix things...
> 
> https://review.openstack.org/#/c/84067/
> 
> 
> Regards,
> 
> 
> Tom
> 
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> 



More information about the Openstack-docs mailing list