Open Stack

The process we're doing is to log a new doc bug with grizzly: as the
first word of the title, either in openstack-manuals or
openstack-api-site. Then we'll do another round to see if the code
itself lands, and triage the doc bug.

I'm about 2 days behind on logging those is all -- and haven't done a
round of triage and checking if the code has landed.

Tom might have more input as well, but that's where those are so far.

Thanks for asking -
Anne

On Sun, Nov 18, 2012 at 12:57 PM, Lorin Hochstein
<lorin at nimbisservices.com> wrote:
> Hi doc folks:
>
> It's great to see that (at least some) developers are using the DocImpact
> flag now when submitting patches. Do we have a way of tracking these the way
> that we do doc bugs? In particular, is there somewhere we could go to see
> the DocImpact-flagged patches and their current status, both from a code
> point of view (in review versus accepted) and from a doc point of view (if a
> corresponding doc patch has been proposed).
>
>
> Take care,
>
> 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
>