Auto update Implementation status for BP away from 'Needs Code Review'
Bug #1220462 reported by
Joe Gordon
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Core Infrastructure |
Confirmed
|
Undecided
|
Thierry Carrez | ||
Bug Description
The 'Implementation' status of 'Needs Code Review' can easily get out of sync with reality. But a bot can go through and change the status of a BP away from 'Needs Code Review' if there are no open patches for that BP.
Revision history for this message
| Thierry Carrez (ttx) wrote | #1 |
| Changed in openstack-ci: | |
| assignee: | nobody → Thierry Carrez (ttx) |
| status: | New → Confirmed |
To post a comment you must log in.
So... the trick is that currently the link between a blueprint and associated reviews is pretty weak. http://
Some projects could require that the branch topic, or a specific header is set in the commit message, and then we could enable auto-updating for that project ?
Ideally we'd have a strong 1:1 link between a blueprint task (think work item) and a review. That's what I'd like to have with Storyboard, although I'm not certain everyone will follow the guidelines enough for automation to start helping us.