2.2.0 (2015-XX-XX)
---------------------
- Support passing in connect_timeout and timeout via _request_options to the Fido and Requests clients

2.1.0 (2015-07-20)
---------------------
- Add warning for deprecated operations

2.0.0 (2015-07-13)
---------------------
- Assume responsibility for http invocation (used to be in bravado-core)

1.1.0 (2015-07-06)
---------------------
- Made bravado compatible with Py34

1.0.0 (2015-06-26)
----------------------
- Fixed petstore demo link
- Pick up bug fixes from bravado-core 1.1.0

1.0.0-rc2 (2015-06-01)
----------------------
- Renamed ResponseLike to IncomingResponse to match bravado-core

1.0.0-rc1 (2015-05-13)
----------------------
- Initial version - large refactoring/rewrite of swagger-py 0.7.5 to support Swagger 2.0

3.0.0 (2015-XX-XX)
---------------------
- Support passing in connect_timeout and timeout via _request_options to the Fido and Requests clients
- Timeout in HTTPFuture now defaults to None (wait indefinitely) instead of 5s. You should make sure
  any calls to http_future.result(..) without a timeout are updated accordingly.

2.1.0 (2015-07-20)
---------------------
- Add warning for deprecated operations

2.0.0 (2015-07-13)
---------------------
- Assume responsibility for http invocation (used to be in bravado-core)

1.1.0 (2015-07-06)
---------------------
- Made bravado compatible with Py34

1.0.0 (2015-06-26)
----------------------
- Fixed petstore demo link
- Pick up bug fixes from bravado-core 1.1.0

1.0.0-rc2 (2015-06-01)
----------------------
- Renamed ResponseLike to IncomingResponse to match bravado-core

1.0.0-rc1 (2015-05-13)
----------------------
- Initial version - large refactoring/rewrite of swagger-py 0.7.5 to support Swagger 2.0

Update changelog with non-backwards compatible functional change to the timeout in HTTPFuture
Update changelog with non-backwards compatible functional change to the timeout in HTTPFuture
