)]}'
{"update.py":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"86feeeb42b425d99872ae1416645ae71a5693cba","unresolved":false,"context_lines":[{"line_number":73,"context_line":"    \u0027them in the order\\n\u0027,"},{"line_number":74,"context_line":"    \u0027# of appearance. Changing the order has an impact on the overall \u0027"},{"line_number":75,"context_line":"    \u0027integration\\n\u0027,"},{"line_number":76,"context_line":"    \u0027# process, which may cause wedges in the gate later.\\n\u0027,"},{"line_number":77,"context_line":"]"},{"line_number":78,"context_line":""},{"line_number":79,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"fa98f980_8ec47760","line":76,"updated":"2014-09-08 13:36:25.000000000","message":"I\u0027ve been seeing this but not sure exactly what it means or when I add a requirement 6 months from now, how do I know if it\u0027s going to cause issues?  I typically either add requirements to the end of the list or place them near similar groups (oslo packages), or sorted alphabetically.\n\nSeems like we need some more wording (or automation) on how to identify a problem before introducing it.","commit_id":"e6c873de4fa007079dd080d19f24908eb25dbc46"}]}