On 10/07/2015 10:42, Robert Collins wrote:
Releasing this on a Friday sounds like bad timing, especially without
advance notice that we'd have to rush to fix the dozens of new issues it
would expose.
There would never be a good time to release such things. The whole
point of the constraints system we're rolling out is to make us not
sensitive to the release schedule of upstreams: we can't dictate the
release schedule of the world to be convenient to our cycles.
I see "mock===1.0.1" in upper-constraints.txt, but the python27 check
job of Swift was broken by the release of mock 1.1.
Can someone please explain me why Swift check job failed?
Patch were I noticed the regression of mock 1.1, on the patch set 6:
https://review.openstack.org/#/c/199034/
(test_wsgi started to fail because the attribute assert_called doesn't
exist.)
My fix for mock 1.1 in Swift:
https://review.openstack.org/#/c/200474/
Victor
__________________________________________________________________________
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
