git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[all] Is there something I can do to get a simple fix done?


I'm struggling to say this positively, but... it feels like OpenStack
promotes refactoring work that will likely break something, but is very
slow when a corresponding fix is needed, even when the fix is trivial.  Is
there something we could do to get fixes done more quickly when needed?

My case in point: my team's networking plugin (networking-calico) does not
do "extraroutes", and so was broken by some python-openstackclient change
(possibly [1]) that wrongly assumed that.  I posted a fix [2] that passed
CI on 21st October, and asked for it to be reviewed on IRC a couple of days
later.  Ã?douard Thuleau posted a similar fix [3] on 4th December, and we
agreed that his was better, so I abandoned mine.  His fix attracted a +2 on
11th December, but has been sitting like that ever since.

It's a fix that I would expect to be simple to review, so I wonder if
there's something else we could have done here to get this moving?  Or if
there is a systemic problem here that deserves discussion?

[1]
https://opendev.org/openstack/python-openstackclient/commit/c44f26eb7e41c28bb13ef9bd31c8ddda9e638862
[2] https://review.opendev.org/#/c/685312/
[3] https://review.opendev.org/#/c/697240/

Many thanks,
    Neil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200106/1c09624e/attachment-0001.html>