)]}'
{"nova/cmd/manage.py":[{"author":{"_account_id":5441,"name":"Andrew Laski","email":"andrew@lascii.com","username":"alaski"},"change_message_id":"7a18590df25384357bc1998e9780934dfcd0125a","unresolved":false,"context_lines":[{"line_number":784,"context_line":"    \"\"\"Class for managing the main database.\"\"\""},{"line_number":785,"context_line":""},{"line_number":786,"context_line":"    online_migrations \u003d ("},{"line_number":787,"context_line":"        db.pcidevice_online_data_migration,"},{"line_number":788,"context_line":"        db.aggregate_uuids_online_data_migration,"},{"line_number":789,"context_line":"        flavor_obj.migrate_flavors,"},{"line_number":790,"context_line":"        flavor_obj.migrate_flavor_reset_autoincrement,"}],"source_content_type":"text/x-python","patch_set":1,"id":"7a8ec9b2_7ad01d54","side":"PARENT","line":787,"updated":"2016-09-20 20:24:04.000000000","message":"Seeing this I think it would help us if from now on each migration had a comment with a born-on or expiration cycle listed.","commit_id":"6d400fb53345eb5c3ab16e59cae1c068b310bfbf"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"f6064f474acf8c5695a19baafacf9cc3e270619f","unresolved":false,"context_lines":[{"line_number":784,"context_line":"    \"\"\"Class for managing the main database.\"\"\""},{"line_number":785,"context_line":""},{"line_number":786,"context_line":"    online_migrations \u003d ("},{"line_number":787,"context_line":"        db.pcidevice_online_data_migration,"},{"line_number":788,"context_line":"        db.aggregate_uuids_online_data_migration,"},{"line_number":789,"context_line":"        flavor_obj.migrate_flavors,"},{"line_number":790,"context_line":"        flavor_obj.migrate_flavor_reset_autoincrement,"}],"source_content_type":"text/x-python","patch_set":1,"id":"5a8bc5a2_14881722","side":"PARENT","line":787,"in_reply_to":"7a8ec9b2_7ad01d54","updated":"2016-09-22 13:12:56.000000000","message":"Yeah, we should probably have a list for each release and add them together or something.","commit_id":"6d400fb53345eb5c3ab16e59cae1c068b310bfbf"}],"releasenotes/notes/removing-pci-parent_addr-migration-f7dfa2b441cf30e8.yaml":[{"author":{"_account_id":5441,"name":"Andrew Laski","email":"andrew@lascii.com","username":"alaski"},"change_message_id":"b95f25c70d1fb986d9985a9053c9a6e8dd9ff23b","unresolved":false,"context_lines":[{"line_number":3,"context_line":"  - In mitaka, an online migration was added to migrate older SRIOV parent"},{"line_number":4,"context_line":"    device information from extra_info to a new column. Since two releases"},{"line_number":5,"context_line":"    have gone out with that migration, it is removed in Ocata and operators"},{"line_number":6,"context_line":"    are expetected to have run it as part of either of the previous two"},{"line_number":7,"context_line":"    releases, if applicable."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"7a8ec9b2_811a986d","line":6,"range":{"start_line":6,"start_character":8,"end_line":6,"end_character":18},"updated":"2016-09-21 18:25:40.000000000","message":"expected","commit_id":"b04a292b56de0aca28335e87fd9ab9f402d02b7e"}]}