So... the trick is that currently the link between a blueprint and associated reviews is pretty weak. http://status.openstack.org/release/ does its best trying to associate the two and still misses quite a few. It also inaccurately reports some reviews as being linked to a blueprint, just because the BP name is mentioned.
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.
So... the trick is that currently the link between a blueprint and associated reviews is pretty weak. http:// status. openstack. org/release/ does its best trying to associate the two and still misses quite a few. It also inaccurately reports some reviews as being linked to a blueprint, just because the BP name is mentioned.
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.