)]}'
{"deliverables/newton/django_openstack_auth.yaml":[{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"8a32dcb7b1ca223f0db4ef8eba98f9d155698a01","unresolved":false,"context_lines":[{"line_number":20,"context_line":"      attribute, redundancy handling for tenant_id usage, and a new"},{"line_number":21,"context_line":"      setting (\"TOKEN_DELETION_DISABLED\") to prevent revocation of"},{"line_number":22,"context_line":"      tokens on logout."},{"line_number":23,"context_line":"  - version: 3.0.0"},{"line_number":24,"context_line":"    projects:"},{"line_number":25,"context_line":"      - repo: openstack/django_openstack_auth"},{"line_number":26,"context_line":"        hash: 7091219cdbac16435c95641d3cce5adcb76d60b7"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5a8bc5a2_5c42f0ae","line":23,"updated":"2016-09-27 13:09:26.000000000","message":"This version number implies there is a backwards-incompatible change in the library, but I don\u0027t see anything obvious like that in the logs. The release is also from a stable branch, and we wouldn\u0027t want to release anything that\u0027s not backwards compatible from the stable branch -- by definition. So if there is something that\u0027s not compatible, it needs to be reverted before we can release.\n\nIf there is nothing incompatible, then the version number should be 2.4.1 to indicate that this is a patch release on the stable branch. In the past we\u0027ve gotten a little confused about whether to go with a minor version bump (2.5.0) because of requirement updates, but we\u0027re settling on just always incrementing the patch version because the requirements \"updates\" are really just syncing up with everything else on the branch and we consider being out of sync a \"bug\".","commit_id":"c4bed838fb3fab3d690b393ae4e0482056fbc689"},{"author":{"_account_id":12826,"name":"Rob Cresswell","display_name":"robcresswell","email":"robert.cresswell@outlook.com","username":"rob-cresswell"},"change_message_id":"6b6f006f0e477b1f9bbca6d11fe4f5752a18b3fb","unresolved":false,"context_lines":[{"line_number":20,"context_line":"      attribute, redundancy handling for tenant_id usage, and a new"},{"line_number":21,"context_line":"      setting (\"TOKEN_DELETION_DISABLED\") to prevent revocation of"},{"line_number":22,"context_line":"      tokens on logout."},{"line_number":23,"context_line":"  - version: 3.0.0"},{"line_number":24,"context_line":"    projects:"},{"line_number":25,"context_line":"      - repo: openstack/django_openstack_auth"},{"line_number":26,"context_line":"        hash: 7091219cdbac16435c95641d3cce5adcb76d60b7"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5a8bc5a2_d776dba2","line":23,"in_reply_to":"5a8bc5a2_5c42f0ae","updated":"2016-09-27 13:16:31.000000000","message":"The difficult commit here is https://github.com/openstack/django_openstack_auth/commit/00346889c99c26f1bbdaf3c392bac6dfefb509c7\n\nThis fixed django 1.10 compatibility, in doing so removed a parameter from a function, but *only when used with django 1.10* (which was unused in anything upstream, but may potentially have been used downstream). This is kind of a grey area, IMO, as this is backwards compatible with any existing installation, but does technically alter an existing function when django runs at 1.10.","commit_id":"c4bed838fb3fab3d690b393ae4e0482056fbc689"}]}