Need autocreation of doc bugs for DocImpact changes.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Core Infrastructure |
Fix Released
|
Low
|
Tom Fifield |
Bug Description
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.
Changed in openstack-ci: | |
status: | Fix Committed → Fix Released |
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.