Need autocreation of doc bugs for DocImpact changes.

[Steven Deaton]

I propose a little extra functionality to the jeepyb repo, whereas the notify_impact script is altered to add the ability to create a bug report automatically, based on the type of impact -- currently, specifically referring to documentation.

This way, not only will an email be sent to the openstack-docs mailing list, but a documentation bug will also be created.

It should be as easy as simply adding another function to notify_impact.py and pulling in the launchpad module for connectivity with the LP API, which is already being done in update_bug anyway.

I'll take care of it, but just wanted to note everything in advance, to see if anyone had anything already developed that could do the same thing.

[James E. Blair (corvus)]

Seems useful. You should chat with the Security Team to see if they want similar functionality; it could be made the default.

Note that you'll need to have it query for existing bugs (possibly by using a tag) to avoid creating a new bug for each new patchset uploaded to existing changes.

Feel free to assign this to yourself when you start working on it.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/32348

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/32348
Committed: http://github.com/openstack-infra/jeepyb/commit/4d05ff14b99f82b96046fd2e949b3ed967c469a0
Submitter: Jenkins
Branch: master

commit 4d05ff14b99f82b96046fd2e949b3ed967c469a0
Author: Steven Deaton <email address hidden>
Date: Mon Jun 10 11:04:16 2013 +1000

    autogenerate doc bug reports based on DocImpact tag

    DocImpact has worked well for communicating new features and code
    changes that impact documentation to the doc team. However, the bulk
    of the emails received were essentially just turned into bug reports.
    This change allows the automated creation of those bug reports.

    The code searches for potential duplicate bugs before creating a bug
    to avoid creating multiple bugs per review.

    Note that this is originally the page from
    https://review.openstack.org/#/c/30718/

    However, I'm drowning in DocImpact emails and wanted to move things
    along while the original author (Steven Deaton) is on holiday.

    There is potential future work here to:
    1) alter the text on bug update
    2) close bugs associated with abandoned patch sets
    3) mark patch-merged bugs as 'confirmed'

    though, as one of the main benefactors from this code, I am quite
    happy to put this forward without these extras initially if it is
    acceptable to our awesome infra team :)

    patchset 2 updates documentation strings thanks to excellent feedback :)

    fixes bug 1184845

    Change-Id: Ia3a8a203314c4e527855df1623491f96da06b882