)]}'
{"features.yaml":[{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"0817ab9bea563b1dce5cb12d676e7fae62239a3c","unresolved":false,"context_lines":[{"line_number":51,"context_line":"  cinder_mn_grenade:"},{"line_number":52,"context_line":"    features: [cinder-mn-grenade]"},{"line_number":53,"context_line":"  cinder_zerodowntime_api:"},{"line_number":54,"context_line":"    features: [cinder-mn-grenade-zerodnupg-api]"},{"line_number":55,"context_line":"  neutron_dvr:"},{"line_number":56,"context_line":"    features: [neutron-dvr]"},{"line_number":57,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":3,"id":"1a430d35_7700a502","line":54,"updated":"2017-02-09 16:41:00.000000000","message":"As the commit message points out, this job is a little more general than just zero-downtime. It\u0027s really testing a specific intermix of API service versions running concurrently... which happens to be driving towards a series of ultimate goals: rolling upgrades, zero-downtime upgrades, and zero-impact upgrades.\n\nFWIW, I think the naming scheme in https://review.openstack.org/#/c/384812/ is a bit better in that it describes the state of the configuration, rather than describing just one feature (i.e. zero-downtime) being tested.","commit_id":"f95605b7a1ed8b37890704cb1ac2cbef99a86c63"}]}