On 09/08/2016 03:59 AM, Ihar Hrachyshka wrote: > I backported the fix to stable/newton: > https://review.openstack.org/#/c/367221/ > > Once it’s in, we’ll trigger another oslo.db release. > > As for the blocking patch for requirements: > https://review.openstack.org/#/c/365565/, I disagree that we should > block oslo.db 4.13.0, because atm pymysql 0.7.7 is blocked in > global-requirements.txt: > > https://github.com/openstack/requirements/blob/4ace2473e4b2eaa283864d74d241c9705f23dd91/global-requirements.txt#L163 > > > and hence there is no known issue with oslo.db 4.13.0 release. I know > there is a patch that unblocks the pymysql release on review: > https://review.openstack.org/#/c/364541/ but it’s not merged right now, > so I don’t see a reason to include block for oslo.db 4.13.0 now. If > anything, it’s that latter patch that should include it. > > The thing is, there is nothing wrong about oslo.db 4.13.0 comparing to > any previous release: all of them are broken with pymysql 0.7.7. If we > are to unblock pymysql 0.7.7 now, we should as well block all previous > releases of oslo.db, meaning bumping the minimal supported version from > 4.10.0+ to 4.13.3+ (when the later is even released; we are still at the > stage of backport). > > Ihar >
Ya that makes sense, the patch can be altered to just block 4.13.1,2 (assuming 4.13.3 really does fix it) -- -- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
