If this is a lone blocker, I also take ownership and volunteer to cut the next RC if it is necessary. :-)

I personally don't see this as a blocker right now, but of course thanks for stepping up!

I understand Andrew G's point about minimizing disruption for users, but if I get this correctly (and I'm hardly the expert here) the behaviour so far has simply been broken.

If we can document a way in the examples and/or release notes to allow people to easily continue with the old behaviour if they wish, that would be helpful. And obviously, it would be good to clarify if we are confident that this behaviour won't change *again* with the change to openstack-swift soon.

ap

Reply via email to